From: "Boris V." <borisvk@bstnet.org>
To: linux-pci@vger.kernel.org
Subject: Re: Kernel 5.9 IOMMU groups regression/change
Date: Tue, 27 Oct 2020 20:31:09 +0100 [thread overview]
Message-ID: <d76b70c1-17f6-60d7-b027-5ecda491101c@bstnet.org> (raw)
In-Reply-To: <74aeea93-8a46-5f5a-343c-790d4c655da3@bstnet.org>
On 25/10/2020 20:45, Boris V. wrote:
> With upgrade to kernel 5.9 my VMs stopped working, because some
> devices can't be passed through.
> This is caused by different IOMMU groups and devices being in the same
> group.
>
> For ex. with kernel 5.8 this are IOMMU groups:
> IOMMU Group 40:
> 08:01.0 PCI bridge [0604]: ASMedia Technology Inc. Device
> [1b21:118f]
> 09:00.0 Ethernet controller [0200]: Intel Corporation I211
> Gigabit Network Connection [8086:1539] (rev 03)
> IOMMU Group 43:
> 0c:00.0 SATA controller [0106]: ASMedia Technology Inc.
> ASM1062 Serial ATA Controller [1b21:0612] (rev 02)
> IOMMU Group 44:
> 0d:00.0 USB controller [0c03]: ASMedia Technology Inc.
> ASM1042A USB 3.0 Host Controller [1b21:1142]
>
> Ethernet, SATA and USB controller in its own group.
>
> And with 5.9, everything is in one group:
> IOMMU Group 29:
> 00:1c.0 PCI bridge [0604]: Intel Corporation C610/X99 series
> chipset PCI Express Root Port #1 [8086:8d10] (rev d5)
> 00:1c.3 PCI bridge [0604]: Intel Corporation C610/X99 series
> chipset PCI Express Root Port #4 [8086:8d16] (rev d5)
> 00:1c.4 PCI bridge [0604]: Intel Corporation C610/X99 series
> chipset PCI Express Root Port #5 [8086:8d18] (rev d5)
> 00:1c.6 PCI bridge [0604]: Intel Corporation C610/X99 series
> chipset PCI Express Root Port #7 [8086:8d1c] (rev d5)
> 07:00.0 PCI bridge [0604]: ASMedia Technology Inc. Device
> [1b21:118f]
> 08:01.0 PCI bridge [0604]: ASMedia Technology Inc. Device
> [1b21:118f]
> 08:03.0 PCI bridge [0604]: ASMedia Technology Inc. Device
> [1b21:118f]
> 08:04.0 PCI bridge [0604]: ASMedia Technology Inc. Device
> [1b21:118f]
> 09:00.0 Ethernet controller [0200]: Intel Corporation I211
> Gigabit Network Connection [8086:1539] (rev 03)
> 0c:00.0 SATA controller [0106]: ASMedia Technology Inc.
> ASM1062 Serial ATA Controller [1b21:0612] (rev 02)
> 0d:00.0 USB controller [0c03]: ASMedia Technology Inc.
> ASM1042A USB 3.0 Host Controller [1b21:1142]
>
>
> This seems to be caused by commit
> 52fbf5bdeeef415b28b8e6cdade1e48927927f60.
> commit 52fbf5bdeeef415b28b8e6cdade1e48927927f60
> Author: Rajat Jain <rajatja@google.com>
> Date: Tue Jul 7 15:46:02 2020 -0700
>
> PCI: Cache ACS capability offset in device
>
> Currently the ACS capability is being looked up at a number of
> places. Read
> and store it once at enumeration so that it can be used by all
> later. No
> functional change intended.
>
> Link:
> https://lore.kernel.org/r/20200707224604.3737893-2-rajatja@google.com
> Signed-off-by: Rajat Jain <rajatja@google.com>
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
>
> drivers/pci/p2pdma.c | 2 +-
> drivers/pci/pci.c | 20 ++++++++++++++++----
> drivers/pci/pci.h | 2 +-
> drivers/pci/probe.c | 2 +-
> drivers/pci/quirks.c | 8 ++++----
> include/linux/pci.h | 1 +
> 6 files changed, 24 insertions(+), 11 deletions(-)
>
>
> If I revert this commit, I get back old groups.
>
> In commit log there is message 'No functional change intended'. But
> there is functional change.
>
> This is Intel Core i7-5930K CPU and X99 chipset. But I see the same
> thing on other Intel systems (didn't test on AMD).
>
>
Some more info.
Problem seems to be that pci_dev_specific_enable_acs() is not called
anymore.
Before, pci_enable_acs() was called from pci_init_capabilities() and in
pci_enable_acs(), pci_dev_specific_enable_acs() was called.
I don't know anything about PCI and this stuff, but I'm guessing that
this function enable ACS for some Intel devices.
But after this commit, pci_acs_init() is called from
pci_init_capabilities() and if pci_find_ext_capability(dev,
PCI_EXT_CAP_ID_ACS) returns 0,
pci_enable_acs() and pci_dev_specific_enable_acs() is not called anymore.
If I apply for ex. this patch bellow, groups are right again and
everything works as before.
diff -ur linux-5.9.1.orig/drivers/pci/pci.c linux-5.9.1/drivers/pci/pci.c
--- linux-5.9.1.orig/drivers/pci/pci.c 2020-10-17 08:31:22.000000000 +0200
+++ linux-5.9.1/drivers/pci/pci.c 2020-10-27 19:01:32.650010803 +0100
@@ -3502,9 +3502,7 @@
void pci_acs_init(struct pci_dev *dev)
{
dev->acs_cap = pci_find_ext_capability(dev, PCI_EXT_CAP_ID_ACS);
-
- if (dev->acs_cap)
- pci_enable_acs(dev);
+ pci_enable_acs(dev);
}
/**
next prev parent reply other threads:[~2020-10-27 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 19:45 Kernel 5.9 IOMMU groups regression/change Boris V.
2020-10-27 19:31 ` Boris V. [this message]
2020-10-28 21:52 ` Bjorn Helgaas
2020-10-28 22:07 ` Rajat Jain
2020-10-28 23:37 ` Rajat Jain
2020-10-29 7:53 ` Boris V.
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=d76b70c1-17f6-60d7-b027-5ecda491101c@bstnet.org \
--to=borisvk@bstnet.org \
--cc=linux-pci@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).