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

[Xen-devel] Interrupt entry points in xen-3.x

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Furquan Shaikh" <furquan.m.shaikh@xxxxxxxxx>
  • Date: Wed, 24 Dec 2008 15:07:25 +0530
  • Delivery-date: Wed, 24 Dec 2008 01:37:49 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=FbFm1D0yZt+qRAH/dTjbrQI9+mFBAFY/WHGDEqsG9xOcp4vTOsnR3ADyXxfOCydHQm OYPxTv/oL0YVQnrBu8aAGU6RexsQH4i/x0zFwqvIZrMKticO/v2GdP2frPz1HHKDgKoF OFsBxFO0K0brSCsg+dHx017M3698np7biO3P4=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I was studying interrupt handling in xen-3.x. I came across "create_bounce_frame" in xen-3.3.0/xen/arch/x86/x86_32/entry.S
I am having some problem understanding the flow of code. Can somebody please give me a step-by-step overview of the flow of interrupt handling right after an interrupt occurs and h/w transfers control to xen. Where is the control passed in xen? (exact entry point)

please help me.

Xen-devel mailing list



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