kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 81841] amd-iommu: kernel BUG & lockup after shutting down KVM guest using PCI passthrough/PCIe bridge
Date: Tue, 09 Sep 2014 15:25:51 +0000	[thread overview]
Message-ID: <bug-81841-28872-KKJZq25HSi@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-81841-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=81841

--- Comment #21 from Marti Raudsepp <marti@juffo.org> ---
(In reply to Joel Schopp from comment #20)
> What updates are you looking for?  Joerg's fix is now upstream.

Yes, but there's still the issue with southbridge component isolation. You
requested more information from me in comment #15 that I provided in comment
#17.

For background see comment #9 from Alex Williamson:
> AMD would need to confirm it.  IOMMU groups are based on hardware advertised
> isolation via the PCIe ACS capability.  Without this, or a device specific
> quirk to take its place, IOMMU groups must assume that peer-to-peer between
> functions of a multi-function device is possible and therefore that the
> devices are not isolated. [...]

> I think the path forward is to get confirmation from AMD that these function
> are isolated from each other and add quirks to the kernel.  Then you won't
> have the device dependencies in vfio-pci.  The override patch allows you to
> do that with just a kernel boot parameter.  There's no gurantee that
> pci-assign will ever be fixed since it's being phased out.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2014-09-09 15:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07 14:45 [Bug 81841] New: amd-iommu: kernel BUG & lockup after shutting down KVM guest using PCI passthrough/PCIe bridge bugzilla-daemon
2014-08-07 14:46 ` [Bug 81841] " bugzilla-daemon
2014-08-07 14:47 ` bugzilla-daemon
2014-08-07 14:47 ` bugzilla-daemon
2014-08-07 15:30 ` bugzilla-daemon
2014-08-07 16:25 ` bugzilla-daemon
2014-08-07 17:56 ` bugzilla-daemon
2014-08-07 18:11 ` bugzilla-daemon
2014-08-07 18:53 ` bugzilla-daemon
2014-08-07 19:47 ` bugzilla-daemon
2014-08-08  2:48 ` bugzilla-daemon
2014-08-08 10:19 ` bugzilla-daemon
2014-08-12  9:36 ` bugzilla-daemon
2014-08-12 10:30 ` bugzilla-daemon
2014-08-12 10:42 ` bugzilla-daemon
2014-08-12 14:53 ` bugzilla-daemon
2014-08-12 15:09 ` bugzilla-daemon
2014-08-12 15:20 ` bugzilla-daemon
2014-09-01  9:30 ` bugzilla-daemon
2014-09-09  7:39 ` bugzilla-daemon
2014-09-09 14:58 ` bugzilla-daemon
2014-09-09 15:25 ` bugzilla-daemon [this message]
2014-10-02 13:30 ` bugzilla-daemon
2014-10-10 15:58 ` bugzilla-daemon

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=bug-81841-28872-KKJZq25HSi@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.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;
as well as URLs for NNTP newsgroup(s).