From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Xen, IRQ-sharing and PCI passthrough Date: Tue, 07 Jul 2009 08:22:40 +0100 Message-ID: References: <20090707081952.5305d4c1@auedv3.syscomp.de> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090707081952.5305d4c1@auedv3.syscomp.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Florian Wagner , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 07/07/2009 07:19, "Florian Wagner" wrote: > My take on this: Xen (or rather the dom0 kernel?) disables the shared > IRQ, which at that time is still in use by the other card. In my case > this crashes the machine, since the IRQ is shared with the RAID > controller (sometimes resulting in destroyed filesystems). > > Is there some other way to fix this than making sure the cards don't > share IRQs (which is quite a hassle when building a significant number > of machines with this configuration but with slightly different > hardware)? A fix from a newer Xen release we could backport to our > Debian kernel perhaps? Newer versions of Xen, and suitably modern ports of the XenLinux patchset, support MSI interrupts. That would avoid the whole issue of interrupt sharing, if either the RIO Specialix or your RAID card supports MSI. Otherwise, can you not rely on cleanly shutting down the domU? Th eproblem is probably that the interrupt line gets wedged high because the domU device has an interrupt pending but the domU is no longer around to service it. -- Keir