From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen-unstable: pci-passthrough "irq 16: nobody cared" on HVM guest shutdown on irq of device not passed through.
Date: Wed, 8 Oct 2014 08:56:53 -0400 [thread overview]
Message-ID: <20141008125653.GA13480@laptop.dumpdata.com> (raw)
In-Reply-To: <543419BB020000780003D026@mail.emea.novell.com>
On Tue, Oct 07, 2014 at 03:50:03PM +0100, Jan Beulich wrote:
> >>> On 07.10.14 at 15:41, <konrad.wilk@oracle.com> wrote:
> > Could you attach also the full dmesg under baremetal with 'debug' and all
> > kinds of debug enabled ? That should help a bit in figuring out why
> > they get MSIs under baremetal but legacy interrupts under Xen.
>
> The messages he sent don't really suggest that. The legacy pin
> based IRQ always gets set up when a device gets enabled, no
> matter whether in the end it would actually get used. And afaict
> other messages clearly hint at MSI being used for the PCIe stuff.
Correct. I fear that in the domain0 we have set an event for this
particular GSI (16) which is also in use in the guest (and then somehow
we did not tear this down when the PCIe setup the MSI).
Xen will send events to both domains - and since domain0 does not
have an IRQ handler for it - it will activate its anti-IRQ storm
routine and disabling the IRQ line.
>
> Jan
>
next prev parent reply other threads:[~2014-10-08 12:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 14:36 Xen-unstable: pci-passthrough "irq 16: nobody cared" on HVM guest shutdown on irq of device not passed through Sander Eikelenboom
2014-09-25 14:42 ` Andrew Cooper
2014-09-25 14:47 ` Sander Eikelenboom
2014-09-25 15:11 ` Jan Beulich
2014-09-25 15:49 ` Sander Eikelenboom
2014-09-25 16:14 ` Jan Beulich
2014-09-25 17:02 ` Sander Eikelenboom
2014-09-25 18:45 ` Sander Eikelenboom
2014-09-25 22:09 ` Sander Eikelenboom
2014-09-26 6:59 ` Jan Beulich
2014-09-26 9:18 ` Sander Eikelenboom
2014-09-26 9:43 ` Jan Beulich
2014-09-26 10:02 ` Sander Eikelenboom
2014-09-26 10:08 ` Jan Beulich
2014-09-27 14:00 ` Sander Eikelenboom
2014-09-27 18:02 ` Konrad Rzeszutek Wilk
2014-09-27 18:23 ` Sander Eikelenboom
2014-10-01 13:52 ` Sander Eikelenboom
2014-10-01 14:19 ` Jan Beulich
2014-10-07 13:41 ` Konrad Rzeszutek Wilk
2014-10-07 14:50 ` Jan Beulich
2014-10-08 12:56 ` Konrad Rzeszutek Wilk [this message]
2014-10-08 20:33 ` Sander Eikelenboom
2014-10-21 13:43 ` Sander Eikelenboom
2014-10-21 14:52 ` Jan Beulich
2014-09-26 6:54 ` Jan Beulich
2014-09-26 9:06 ` Sander Eikelenboom
2014-09-26 6:50 ` Jan Beulich
2014-09-26 9:00 ` Sander Eikelenboom
2014-09-26 9:09 ` Jan Beulich
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=20141008125653.GA13480@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xenproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).