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

[Xen-devel] Physical Interrupt


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Jingwei Tan <efundaism@xxxxxxxxx>
  • Date: Fri, 8 May 2009 10:05:47 +0800
  • Delivery-date: Thu, 07 May 2009 19:06:43 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=lXrFbr13gYVRGHeM9QD3aKi6sCKn8eYOtf0jdbQ9l8jrufkoQiyHys9b6ecYaVQzlx jrm5XzNFtyK8D5se32JDHZVzdD3lb2L0bsv2wdz44QQ9gWAs/im/tDHOTEbw+hwl8dXR xH/VwUOTys8Fc/ESf/uqqIZeUjGHR8glq15qI=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hey Peeps,

Quoted from the Interface Manual:
"Interrupts are virtualized by mapping them to events, which are delivered asynchronously to the target domain using a callback supplied via the set callbacks() hypercall. A guest OS can map these events onto its standard interrupt dispatch mechanisms. Xen
is responsible for determining the target domain that will handle each physical interrupt source."

"Xen is responsible for determining the target domain that will handle each physical interrupt source"

Is there a way to modify the source of Xen to make is such that:
All physical interrupt will be directed to all domains?

Thanks in advance. =)

--
Tan
_______________________________________________
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®.