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] PCI passthrough w/ shared IRQ in xen/master

To: Mark Hurenkamp <mark.hurenkamp@xxxxxxxxx>, Michael D Labriola <mlabriol@xxxxxxxx>
Subject: Re: [Xen-devel] PCI passthrough w/ shared IRQ in xen/master
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 19 Feb 2010 16:24:28 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 19 Feb 2010 08:26:35 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <edac2478c2d590b412002a436ef846dc.squirrel@xxxxxxxxxxxxxxxxx>
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
Thread-index: AcqxfuU7E0djWbB1TOaOeGBVcTNJzgAARy13
Thread-topic: [Xen-devel] PCI passthrough w/ shared IRQ in xen/master
User-agent: Microsoft-Entourage/12.23.0.091001
On 19/02/2010 16:15, "Mark Hurenkamp" <mark.hurenkamp@xxxxxxxxx> wrote:

> When you do passthrough the device which has a shared IRQ, the domU will
> load the appropriate driver, but Xen refuses to assign the IRQ to the
> domU.
> In your case (and mine as well), the driver in domU is not aware that it
> has no IRQ, and thus starts generating interupts which are then caught by
> Dom0 as spurious interrupts, in my case even causing Dom0 to crash at
> times.

Are you sure the domU doesn't get the interrupts as well? Correct behaviour
in Xen will be to send the interrupt to both dom0 and domU - since Xen can't
work out which of the two it properly belongs to (and it could be both).

I would suggest try commenting out the content of the function
kernel/irq/spurious.c:note_interrupt(). That will stop dom0 from reacting to
the 'spurious' irqs that it sees and ignore them instead. See if that works
for you.

 -- Keir

> My way around this, is to try and move the other device IRQs out of the
> way (the ones that matter seem to be MSI capable), but i understand that's
> not always possible.
> If your other device is PCI based, and has no MSI, then for now I'm
> affraid you're out of luck...
> 
> Like you, I do hope this is considered a bug that will be fixed in a later
> release... anyone know what the xen policy is on this?



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