[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] interrupt handling in xen


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Diwaker Gupta <diwaker.lists@xxxxxxxxx>
  • Date: Tue, 6 Sep 2005 11:00:17 -0700
  • Delivery-date: Tue, 06 Sep 2005 17:58:12 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=uSNeVh1Z7zRGi3vEtI2mkEhwxVzwof1t8hwRdF2Scrta854JRfjw/OsKyHWUHC6vdZfj8biwvnjlZzzabfD5zpzQxDes1kWhp0SItriGhiU/3lKt+RJAv1JWUF6Zx7Hu+DHoGK7XABCDzNITiDbIkfTYWHwfLPuUZM/NYMUlsnw=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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
-- 
Web/Blog/Gallery: http://floatingsun.net

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.