 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] Physical Interrupt
| To: | xen-devel@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-devel] Physical Interrupt |
| From: | Jingwei Tan <efundaism@xxxxxxxxx> |
| Date: | Fri, 8 May 2009 10:05:47 +0800 |
| Delivery-date: | Thu, 07 May 2009 19:06:43 -0700 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=U5nhoAn34vbXSUWohHgUWE9+rOqRLVSYCfjxWKWtFz0=; b=VfXi1LuUz9X8LD9MiSepaP38FkX0EPaDSw6bF7dVucDoAwjrUnNWqNSxNP1f89CgcF nfSlhplWvSal/dhLtbsBrd+jljNDjcD8Og0v5L9R8KJWIWKcBY25y5llZ1IdiV0tqteB La4CBqQbprta1TZ3KQKvzrG3e0zBZFYhLR1uo= |
| 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= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] [PATCH][ioemu] fix PCI bar mapping, Simon Horman |
|---|---|
| Next by Date: | RE: [Xen-devel] [PATCH][ioemu] fix PCI bar mapping, Cui, Dexuan |
| Previous by Thread: | [Xen-devel] [GIT PULL] xen: swiotlb support for Xen dom0, Jeremy Fitzhardinge |
| Next by Thread: | [Xen-devel] [BISECTED REGRESSION] Xen: OOPSes on heavy block IO on 2.6.30-master, Bryan Donlan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
