>
> On 18/8/08 13:19, "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
wrote:
>
> > Just so I understand, even if I see the IRQ on CPU1, I should always
> > treat it as if it came in on CPU0?
>
> Yes. Only vcpu0's event-channel logic is wired into the virtual
> PIC/IOAPIC.
> Even if the IOAPIC then forwards the interrupt to a different VCPU,
it's
> still vcpu0's event-channel status that initiated the interrupt. Other
> vcpus' event-channel statuses do not cause interrupts in HVM.
>
I'm not sure if this is a general or a windows specific question, but I
can approach this in one of two ways...
1. Make sure the interrupt is only ever delivered to CPU0 by specifying
the affinity when I call IoConnectInterrupt
2. Accept the interrupt on any CPU but always use vcpu_info[0] to check
the flags etc.
Does the hypervisor make any scheduling assumptions upon delivering an
event to a domain? (eg does it schedule CPU0 on the basis that that CPU
is going to be handling the event?)
Thanks
James
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel