From mboxrd@z Thu Jan  1 00:00:00 1970
From: Diwaker Gupta <diwaker.lists@gmail.com>
Subject: interrupt handling in xen
Date: Tue, 6 Sep 2005 11:00:17 -0700
Message-ID: <891be94105090611004c3692f@mail.gmail.com>
Reply-To: diwaker.lists@gmail.com
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
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: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

I'm trying to understand interrupt handling in Xen (as described in
the "Restructuring I/O" techreport). But I'm having a hard time
finding all the bits and pieces in the code.

For instance, the text says "a device's interrupt line triggers
execution of a stub routing within  Xen rather than causing immediate
entry into the domain that is managing that device". Can someone point
me to the code where this takes place?

TIA
--=20
Web/Blog/Gallery: http://floatingsun.net