From mboxrd@z Thu Jan 1 00:00:00 1970 From: Himanshu Raj Subject: Re: driver domains Date: Tue, 18 Jul 2006 18:41:33 -0400 Message-ID: <20060718224133.GI28405@cc.gatech.edu> References: <44BD293B.8010306@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <44BD293B.8010306@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Mike D. Day" Cc: Xen Mailing List List-Id: xen-devel@lists.xenproject.org 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. -------------------------------------------------------------------------