driver domains

driver domains

[valerie galey]

[-- Attachment #1: Type: text/plain, Size: 223 bytes --]

     In the Xen Roadmap Overviewew I found that drivers for block and network devices will be moving out of Xen and into 'driver domains'. 
     What you mean by "drivers domains"? 
    
    Best Regards.
    Valerie.

[-- Attachment #2: Type: text/html, Size: 862 bytes --]

driver domains

[Muli Ben-Yehuda]

Ian,

You mentioned during the summit that there are several driver domains
patches floating around and one is likely to go in soon (apologies if
I misunderstood). Could you or the author please post it? we'd like to
give it a spin as soon as possible.

Cheers,
Muli
-- 
Muli Ben-Yehuda
http://www.mulix.org | http://mulix.livejournal.com/

Re: driver domains

[Keir Fraser]

On 25 Jan 2006, at 18:24, Muli Ben-Yehuda wrote:

> You mentioned during the summit that there are several driver domains
> patches floating around and one is likely to go in soon (apologies if
> I misunderstood). Could you or the author please post it? we'd like to
> give it a spin as soon as possible.

I've just emailed the author to encourage him to post the patches to 
xen-devel as the next stage towards getting the patches checked in.

  -- Keir

Re: driver domains

[Jon Mason]

On Wed, Jan 25, 2006 at 06:49:01PM +0000, Keir Fraser wrote:
> 
> On 25 Jan 2006, at 18:24, Muli Ben-Yehuda wrote:
> 
> >You mentioned during the summit that there are several driver domains
> >patches floating around and one is likely to go in soon (apologies if
> >I misunderstood). Could you or the author please post it? we'd like to
> >give it a spin as soon as possible.
> 
> I've just emailed the author to encourage him to post the patches to 
> xen-devel as the next stage towards getting the patches checked in.

I'll be happy to give it a quick sniff once it is posted.

Thanks,
Jon

driver domains

[Mike D. Day]

For a driver domain, do interrupts for the devices that service that 
domain get handled by the driver domain itself, or by domain 0 first?

Which code should I read to understand how this works?

thanks,

Mike Day

Re: driver domains

[Himanshu Raj]

Hi Mike,

Interrupts are passed on to the domain that registers the irq handler (and
only priviledged domains are allowed to do so). Hence the interrupt would be
sent directly to driver domain (unless it is being shared by multiple domains,
in which case it would go to all the domains).

A good start would be to look at xen/arch/x86/irq.c, specifically at pirq_guest_bind,
pirq_guest_unbind and __do_IRQ_guest.

HTH,
-Himanshu

On Tue, Jul 18, 2006 at 02:32:27PM -0400, Mike D. Day wrote:
> For a driver domain, do interrupts for the devices that service that 
> domain get handled by the driver domain itself, or by domain 0 first?
> 
> Which code should I read to understand how this works?
> 
> thanks,
> 
> Mike Day
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

-- 
-------------------------------------------------------------------------
Himanshu Raj
PhD Student, GaTech (www.cc.gatech.edu/~rhim)
I prefer to receive attachments in an open, non-proprietary format.
-------------------------------------------------------------------------

RE: driver domains

[Ian Pratt]

> For a driver domain, do interrupts for the devices that service that
> domain get handled by the driver domain itself, or by domain 0 first?

They are fielded by Xen then passed on as events direct to the domain.
If the line is shared, it will send events to both domains (though
interrupt sharing should be avoided).

Dom0 is only involved with the interrupt 'plumbing', when the interrupt
is first configured.

Ian 

Re: driver domains

[Mike D. Day]

Himanshu Raj wrote:
> Hi Mike,
> 
> Interrupts are passed on to the domain that registers the irq handler (and
> only priviledged domains are allowed to do so). Hence the interrupt would be
> sent directly to driver domain (unless it is being shared by multiple domains,
> in which case it would go to all the domains).
> 
> A good start would be to look at xen/arch/x86/irq.c, specifically at pirq_guest_bind,
> pirq_guest_unbind and __do_IRQ_guest.
> 

Himanshu thanks to you and Ian for responding!

Mike