From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>, Florian Wagner <f_wagner@syscomp.de>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen, IRQ-sharing and PCI passthrough
Date: Tue, 07 Jul 2009 08:39:22 +0100 [thread overview]
Message-ID: <C678BA3A.EFC8%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4A53162C02000078000091BE@vpn.id2.novell.com>
On 07/07/2009 08:32, "Jan Beulich" <JBeulich@novell.com> wrote:
>>>> Florian Wagner <f_wagner@syscomp.de> 07.07.09 08:19 >>>
>> 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?
>
> Assuming your kernel has a call to irq_ignore_unhandled() out of
> note_interrupt(), there's nothing but using hardware's help (i.e. VT-d
> interrupt remapping) to get this addressed: The pv passthrough
> mechanism assumes that guests you assign physical devices to are well
> behaved, and your guest isn't (it fails to disable the interrupt at the
> device).
Another thought is that the toolstack should be trying to reset the device
during domain destroy. I'm not certain that's always possible and always
done though (HVM passthru is better tested than PV passthru).
-- Keir
next prev parent reply other threads:[~2009-07-07 7:39 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
2009-07-07 7:32 ` Jan Beulich
2009-07-07 7:39 ` Keir Fraser [this message]
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=C678BA3A.EFC8%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=JBeulich@novell.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.