All of lore.kernel.org
 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, 12 Aug 2014 15:09:44 +0000	[thread overview]
Message-ID: <bug-81841-28872-jANQWSGbZg@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 #16 from Alex Williamson <alex.williamson@redhat.com> ---
(In reply to Joel Schopp from comment #15)
> > (In reply to Joel Schopp from comment #10)
> > > > AMD would need to confirm it.
> > >
> > > I don't have an answer for you offhand.  Let me do some digging and get you
> > > an answer.
> > 
> > I am sorry if I sounded frustrated or arrogant earlier. Any update on this?
> 
> It's not clear to me which devices were being put in the same group.  Here's
> some of my notes on your lspci output

Marti, the output of 'find /sys/kernel/iommu_groups' would be useful here. 
I'll try to help based on what I think is happening...

> lspci -vt
> -[0000:00]-+-00.0  Advanced Micro Devices, Inc. [AMD] Device 1422
>            +-00.2  Advanced Micro Devices, Inc. [AMD] Device 1423
>            +-01.0  Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7
> 200 Series]
>            +-01.1  Advanced Micro Devices, Inc. [AMD/ATI] Device 1308
>            +-02.0  Advanced Micro Devices, Inc. [AMD] Device 1424
>            +-03.0  Advanced Micro Devices, Inc. [AMD] Device 1424
>            +-04.0  Advanced Micro Devices, Inc. [AMD] Device 1424
>            +-10.0  Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller
>            +-10.1  Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller
> 
> These xhci controllers are isolated from from the other devices, I would
> need some more detail on which variant you are running to determine if they
> are isolated from eachother, they probably aren't.

10.0 & 10.1 will typically be grouped together due to lack of ACS.  This is
usually not a problem.

>            +-11.0  Advanced Micro Devices, Inc. [AMD] FCH SATA Controller
> [AHCI mode]
> The sata controller is isolated from the other devices

Yep, and it's a single function device so IOMMU groups should be ok.

>            +-12.0  Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller
>            +-12.2  Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller
> This pair of OHCI/EHCI controllers are together isolated from the other
> devices

Yep, same as above.

>            +-13.0  Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller
>            +-13.2  Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller
> This pair of OHCI/EHCI controllers are together isolated from the other
> devices

Yep

>            +-14.0  Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller
>            +-14.1  Advanced Micro Devices, Inc. [AMD] FCH IDE Controller
>            +-14.2  Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller
>            +-14.3  Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge
> I do not think the SMBus/IDE/Azalia/LPC are isolated from eachother, but
> they are isolated from the other devices I have identified.
> 
> 
>            +-14.4-[01]----05.0  Dialogic Corporation PRI
> The legacy PCI should be isolated from the other devices identified.  Not
> sure what is going on here.
> 
>            +-14.5  Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller
> This OHCI Controller should also be isolated from the other devices.

All of the above will be grouped together, this is the problem.  Since none of
these functions support ACS, IOMMU groups assume that peer-to-peer between
functions is possible.  If 14.4 and 14.5 are truly isolated from the rest of
the package then we should have quirks to support that.  This whole block is an
update or the quirk already shown in comment 7.

>            +-15.0-[02]--
>            +-15.2-[03]----00.0  ASMedia Technology Inc. ASM1042 SuperSpeed
> USB Host Controller
> Is this in a PCI-e slot or otherwise attached to the PCI-e?
> 
>            +-15.3-[04]----00.0  Qualcomm Atheros QCA8171 Gigabit Ethernet
> Is this in a PCI-e slot or otherwise attached to the PCI-e?

I would guess 15.x are all PCIe root ports, hopefully with ACS support.

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

  parent reply	other threads:[~2014-08-12 15:09 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 [this message]
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
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-jANQWSGbZg@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 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.