[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v7 15/17] vmx: VT-d posted-interrupt core logic handling
On 09/17/2015 10:38 AM, George Dunlap wrote: > Is it the case that the interrupt is not actually delivered to the > processor, but that the pending bit will be set in the pi field, so that > the interrupt will be delivered the next time the hypervisor returns > into the guest? > > (I am assuming that is the case, because if the hypervisor *does* get an > interrupt, then it can just unblock it there.) Actually, it looks like you *do* in fact get a pi_notification_interrupt() in this case. Could we to check to see if the current vcpu is blocked and unblock it? I haven't yet decided whether I prefer my original suggestion of switching the interrupt and putting things on the wake-up list in vcpu_block(), or of deferring adding things to the wake-up list until the actual context switch. -George _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |