All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Florian Wagner <f_wagner@syscomp.de>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen, IRQ-sharing and PCI passthrough
Date: Tue, 07 Jul 2009 08:22:40 +0100	[thread overview]
Message-ID: <C678B650.EFBC%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <20090707081952.5305d4c1@auedv3.syscomp.de>

On 07/07/2009 07:19, "Florian Wagner" <f_wagner@syscomp.de> 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

  reply	other threads:[~2009-07-07  7:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07  6:19 Xen, IRQ-sharing and PCI passthrough Florian Wagner
2009-07-07  7:22 ` Keir Fraser [this message]
2009-07-07  7:32 ` Jan Beulich
2009-07-07  7:39   ` Keir Fraser
2009-07-08  6:35   ` Florian Wagner
2009-07-08  7:31     ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C678B650.EFBC%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=f_wagner@syscomp.de \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.