[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] fooey. no interrupts.
On Tue, 10 Aug 2004, Keir Fraser wrote:
> > > 4. The original value of vcpu_data.evtchn_upcall_pending must be zero.
> > > 5. The value of vcpu_data.evtchn_upcall_mask must be zero.
> > OK, this I don't totally see. From the code I posted before, it seems to
> > me only the first three conditions matter.
> The first three conditions cause us to decide whether or not to
> schedule the target domain, sending a cross-cpu interrupt if
> necessary. The final two are checks just before calling back to the
> guest OS, just to check whether it is in a position to receive async
Keir, I don't see that in the code and Christian sent a note that left me
thinking it does not work that way.
as Christian said, (4) doesn't do anything conditional, it does this:
/* The VCPU pending flag must be set /after/ update to
s->vcpu_data.evtchn_upcall_pending = 1;
which looks pretty unconditional to me. Is there something else I'm
LANL CCS-1 email flavor:
***** Correspondence 
***** DUSA LACSI-HW [x ]
***** DUSA LACSI-OS [ ]
***** DUSA LACSI-CS [ ]
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
Xen-devel mailing list