[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] [VTD][patch 0/5] HVM device assignment using vt-d

  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>
  • Date: Wed, 30 May 2007 15:02:59 -0700
  • Delivery-date: Wed, 30 May 2007 15:01:12 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acei7YJ0pr6pL1ntT2Wzdmq3YT+WeAABwdLMAAN25GA=
  • Thread-topic: [Xen-devel] [VTD][patch 0/5] HVM device assignment using vt-d

>How does this new scheme work? Can it supplant the 
>ioapic_ack=new method?
>Clearly requiring the use of a hacky command-line option to 
>make use of a
>new core feature is not very nice to say the least.

Basically, the calls to mask_IO_APIC_irq()/unMask_IO_APIC_irq()
in arch/x86/io_apic.c were replaced with
- where the fake vector is an unused vector.

Since the global interrupt from chipset only occurs during
masked interrupts, this avoids that chipset bug that cause
you to switch to ioapic_ack=new last year.  I believe it can
supplant ioapic_ack=new method.

>I would expect it to work (by design at least) even with 

We based our enabling effort on ioapic_ack=old so far.
In theory, it should work with ioapic_ack=new.  I have tried
Ioapic_ack=new but it is not working right now.  We will
be looking into this.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.