Re: Dynamic-irq's in HVM domains

[Mark Williamson <mark.williamson@cl.cam.ac.uk>]

> > I can't help with the Windows side I'm afraid, perhaps there is a
> > windows dev newsgroup or something that might be useful?
>
> There might be. Curiously, windows communities are a bit different...
> people like to keep their cards closer to their chest :)
>
> > On Fri, 2007-11-30 at 20:02 +1100, James Harper wrote:
> > > I made the assumption that 'Dynamic-irq' is the same as virq... if
> > > not, what is a virq? It appears to be something that the hypervisor
>
> is
>
> > > aware of as there is a hypercall to bind to one.
> >
> > They are IRQ sources from the hypervisor (as opposed to from a virtual
> > or physical device or another domain). From xen/include/public/xen.h:
>
> <snip>
>
> > They are used by binding them to an event channel using
> > EVTCHNOP_bind_virq, as you've probably noticed.
>
> Ah. I had them backwards. I was assuming you could say 'when an event
> channel fires, call this virq instead' and the virq would jump somewhere
> into your idt.
>
> I'll keep searching for another way...

Doesn't windows have some kind of deferred work processing like Linux softirqs 
or workqueues that you could used to schedule work to happen soon in driver 
context?  That'd enable you to do everything within existing windows APIs.

Afraid I've not done any Windows development, either ;-)

Cheers,
Mark

-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!