From: Maor Gottlieb <maorg@nvidia.com>
To: Shlomo Pongratz <shlomopongratz@gmail.com>, <linux-pci@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <andrew.maier@eideticom.com>,
<logang@deltatee.com>, <bhelgaas@google.com>, <jgg@nvidia.com>,
<helgaas@kernel.org>, Shlomo Pongratz <shlomop@pliops.com>
Subject: Re: [PATCH V7 1/1] Intel Sky Lake-E host root ports check.
Date: Mon, 11 Apr 2022 17:03:55 +0300 [thread overview]
Message-ID: <92621dc1-5b9d-8e5c-acbf-fff3a0ea0fd8@nvidia.com> (raw)
In-Reply-To: <20220410105213.690-2-shlomop@pliops.com>
> diff --git a/drivers/pci/p2pdma.c b/drivers/pci/p2pdma.c
> index 30b1df3c9d2f..187047be83a0 100644
> --- a/drivers/pci/p2pdma.c
> +++ b/drivers/pci/p2pdma.c
> @@ -327,15 +327,19 @@ static const struct pci_p2pdma_whitelist_entry {
>
> /*
> * This lookup function tries to find the PCI device corresponding to a given
> - * host bridge.
> + * host bridge or a root port.
> *
> * It assumes the host bridge device is the first PCI device in the
> - * bus->devices list and that the devfn is 00.0. These assumptions should hold
> - * for all the devices in the whitelist above.
> + * bus->devices list and that the devfn is 00.0. The first assumption should
> + * hold for all the devices in the whitelist above, however the second
> + * assumption doesn't always hold for root ports.
> + * For example for Intel Skylake devices 2030, 2031, 2032 and 2033,
> + * which are root ports (A, B, C and D respectively).
> + * So the function checks explicitly that the device is a root port.
> *
> - * This function is equivalent to pci_get_slot(host->bus, 0), however it does
> - * not take the pci_bus_sem lock seeing __host_bridge_whitelist() must not
> - * sleep.
> + * This function is equivalent to pci_get_slot(host->bus, 0) (except for
> + * the root port test), however it does not take the pci_bus_sem lock seeing
> + * __host_bridge_whitelist() must not sleep.
> *
> * For this to be safe, the caller should hold a reference to a device on the
> * bridge, which should ensure the host_bridge device will not be freed
> @@ -350,10 +354,19 @@ static struct pci_dev *pci_host_bridge_dev(struct pci_host_bridge *host)
>
> if (!root)
> return NULL;
> - if (root->devfn != PCI_DEVFN(0, 0))
> - return NULL;
>
> - return root;
> + /* Verify that the device is a host bridge or a root port
> + * It is assumed that host bridges have a 0 devfn, (common practice)
> + * but some of the entries in the whitelist are root ports that can
> + * have any devfn
> + */
> + if (root->devfn == PCI_DEVFN(0, 0))
> + return root;
> +
> + if (pci_pcie_type(root) == PCI_EXP_TYPE_ROOT_PORT)
> + return root;
> +
> + return NULL;
> }
>
> static bool __host_bridge_whitelist(struct pci_host_bridge *host,
Thanks, it also helped our system.
Tested-by: Maor Gottlieb <maorg@nvidia.com>
next prev parent reply other threads:[~2022-04-11 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 10:52 [PATCH V7 0/1] Intel Sky Lake-E host root ports check Shlomo Pongratz
2022-04-10 10:52 ` [PATCH V7 1/1] " Shlomo Pongratz
2022-04-11 14:03 ` Maor Gottlieb [this message]
2022-04-11 19:10 ` Bjorn Helgaas
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=92621dc1-5b9d-8e5c-acbf-fff3a0ea0fd8@nvidia.com \
--to=maorg@nvidia.com \
--cc=andrew.maier@eideticom.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=shlomop@pliops.com \
--cc=shlomopongratz@gmail.com \
/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