From: Thomas Gleixner <tglx@linutronix.de>
To: Jason Taylor <jason.taylor@simplivity.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
x86@kernel.org, Jiang Liu <jiang.liu@linux.intel.com>
Subject: Re: VMware PCI passthrough regression
Date: Thu, 14 Jan 2016 22:15:59 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1601142144310.3575@nanos> (raw)
In-Reply-To: <4113b621e0f94c26b28ed1f80979287f@WB-SVT-EXBE03.simplivity.com>
Jason,
On Thu, 14 Jan 2016, Jason Taylor wrote:
> I've run into a regression using PCI passthrough with the 4.4
> kernel.
Actually that is a 4.2 kernel according to the dmesg in the bug tracker.
> Attempting to passthrough an LSI card with ESXi version 6. Seeing
> timeouts and oops in the log and the disks do not show up.
The timeouts are probably related to missing irq delivery, so it might be
related to the big overhaul of the x86 irq subsystem.
The oops is a genuine driver bug probably unearthed by the irq issue. That
should be reported seperately to the megasas folks.
> I performed a bisect which tracked down the issue to the commit below.
>
> More details are available in a bug report I filed with Ubuntu:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1528849
>
> commit 52f518a3a7c2f80551a38d38be28bc9f335e713c
> x86/MSI: Use hierarchical irqdomains to manage MSI interrupts
I have no idea how that breaks the vmware passthrough. Can you please verify
- whether that kernel works on the real hardware with that LSI card
- whether that kernel works in a KVM guest with that card passed through
If one of those things break, we can certainly help to analyse that. If not,
then you need to talk to vmware.
Thanks,
tglx
next parent reply other threads:[~2016-01-14 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4113b621e0f94c26b28ed1f80979287f@WB-SVT-EXBE03.simplivity.com>
2016-01-14 21:15 ` Thomas Gleixner [this message]
2016-02-12 0:43 ` Jason Taylor
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=alpine.DEB.2.11.1601142144310.3575@nanos \
--to=tglx@linutronix.de \
--cc=jason.taylor@simplivity.com \
--cc=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®