From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Mike D. Day" <ncmike@us.ibm.com>
Subject: Re: driver domains
Date: Tue, 18 Jul 2006 19:10:21 -0400
Message-ID: <44BD6A5D.8040307@us.ibm.com>
References: <44BD293B.8010306@us.ibm.com>
	<20060718224133.GI28405@cc.gatech.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20060718224133.GI28405@cc.gatech.edu>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Himanshu Raj <rhim@cc.gatech.edu>
Cc: Xen Mailing List <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

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