Re: [Xen-devel] fooey. no interrupts.

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

> On Mon, 9 Aug 2004, Keir Fraser wrote:
> 
> > Unmasking evtchn_upcall_mask and evtchn_mask[] need special attention
> > because a pending interrupt will not automatically get raised as it
> > would on real hardware ---- think of it like an edge-triggered
> > interrupt where you lost the edge because the line was masked. So what
> > we do in Linux is:
> 
> in any event, if clock interrupts are enabled, shouldn't I get an 
> interrupt 500 ms later? Or am I misreading the code.

Yes, you'll get the interrupt sometime later, the next time Xen is
returning execution to you.

 -- Keir


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel