From: Shlomo Pongratz <shlomopongratz@gmail.com>
To: 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: [PATCH V7 0/1] Intel Sky Lake-E host root ports check.
Date: Sun, 10 Apr 2022 13:52:12 +0300 [thread overview]
Message-ID: <20220410105213.690-1-shlomop@pliops.com> (raw)
Changes in v7:
Apply Bjorn Helgaas suggestion to avoid negative logic.
Changes in v6:
Address Bjorn Helgaas comments, e.g. commit line length and using both
"Sky Lake-E" and "SkyLake-E" in comments.
The comments in the code now use Skylake.
However the patch subject still refers to "Sky Lake-E" since
Andrew Maier's original patch used that name.
Changes in v5:
Address Logan Gunthorpe, Jason Gunthorpe and Bjorn Helgaas comments.
Fix indentation.
Update comments.
Changes in v4:
Address Bjorn Helgaas and Jason Gunthorpe comments.
Replace the implementation of pci_is_root_port with a simple check
pci_pcie_type(root) != PCI_EXP_TYPE_ROOT_PORT and remove the added
IS_ROOT_PORT flag.
Update patch text.
Changes in v3:
Use Jason Gunthorpe suggestion, that is add a flag 'IS_ROOT_PORT'
instead of 'port' and then just ignore the slot number entirely for root
ports.
Changes in v2:
Change comment and description based on Logan Gunthorpe comments.
v1:
In commit 7b94b53db34f ("PCI/P2PDMA: Add Intel Sky Lake-E Root Ports B, C,
D to the whitelist")
Andrew Maier added the Sky Lake-E additional devices
2031, 2032 and 2033 root ports to the already existing 2030 device.
The Intel devices 2030, 2031, 2032 and 2033 which are root ports A, B, C
and D, respectively and if all exist they will occupy slots 0 till 3 in
that order.
The original code handled only the case where the devices in the whitelist
are host bridges and assumed that they will be found on slot 0.
Since this assumption doesn't hold for root ports, add a test to cover this
case.
Shlomo Pongratz (1):
Intel Sky Lake-E host root ports check.
drivers/pci/p2pdma.c | 31 ++++++++++++++++++++++---------
1 file changed, 22 insertions(+), 9 deletions(-)
--
2.17.1
next reply other threads:[~2022-04-10 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 10:52 Shlomo Pongratz [this message]
2022-04-10 10:52 ` [PATCH V7 1/1] Intel Sky Lake-E host root ports check Shlomo Pongratz
2022-04-11 14:03 ` Maor Gottlieb
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=20220410105213.690-1-shlomop@pliops.com \
--to=shlomopongratz@gmail.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 \
/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