WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [PATCH] xen: fix interrupt routing

To: Alexander Graf <agraf@xxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] xen: fix interrupt routing
From: Avi Kivity <avi@xxxxxxxxxx>
Date: Wed, 15 Jun 2011 19:34:25 +0300
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>, Jan Kiszka <jan.kiszka@xxxxxxxxxxx>, "qemu-devel@xxxxxxxxxx" <qemu-devel@xxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, Isaku Yamahata <yamahata@xxxxxxxxxxxxx>, Anthony Liguori <anthony@xxxxxxxxxxxxx>
Delivery-date: Wed, 15 Jun 2011 09:35:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <DCAB4C78-3A84-41F0-8074-3E2712F60EE4@xxxxxxx>
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>
References: <alpine.DEB.2.00.1105261645560.12963@kaball-desktop> <21A10B78-49E2-453B-8AE6-48155E2071B5@xxxxxxx> <alpine.DEB.2.00.1105311123210.12963@kaball-desktop> <68B936C0-E230-4B48-A274-CB875ED92D5E@xxxxxxx> <1308053820.17937.72.camel@xxxxxxxxxxxxxxxxxxxxxx> <1D2C3E16-193F-4EEC-B7EF-AE038B4F2EE9@xxxxxxx> <alpine.DEB.2.00.1106141344260.12963@kaball-desktop> <4DF77E8E.40806@xxxxxxxxxxx> <alpine.DEB.2.00.1106141658180.12963@kaball-desktop> <DCAB4C78-3A84-41F0-8074-3E2712F60EE4@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc15 Lightning/1.0b3pre Thunderbird/3.1.10
On 06/15/2011 11:24 AM, Alexander Graf wrote:
I'm actually not quite sure what exactly he's describing here. But if it's 
bypassing the bus logic, it's not a normal PCI device :). Sure, there are 
special case devices that also expose a PCI interface. But real PCI cards that 
you plug in onto the PCI bus can't bypass the interrupt logic of the bus, as 
the only interrupt wires they have go to the bus. And since the PCI adapters we 
use in PC machines in Qemu are all non-special, guests can possibly choke on 
this.


There actually is a special device in qemu - acpi power management is configured as a PCI device, but its interrupt is hard-wired to gsi 9 and is edge-triggered (so it can't share the irq line).

I other devices that are special in this regard to also be part of the chipset, not devices you can plug into arbitrary slots.

--
error compiling committee.c: too many arguments to function


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