From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Gerd Bayer <gbayer@linux.ibm.com>
Cc: Hans Zhang <18255117159@163.com>,
lpieralisi@kernel.org, kwilczynski@kernel.org,
bhelgaas@google.com, helgaas@kernel.org, jingoohan1@gmail.com,
mani@kernel.org, robh@kernel.org, schnelle@linux.ibm.com,
Lukas Wunner <lukas@wunner.de>,
arnd@kernel.org, geert@linux-m68k.org,
linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v15 1/6] PCI: Clean up __pci_find_next_cap_ttl() readability
Date: Wed, 20 Aug 2025 14:36:19 +0300 (EEST) [thread overview]
Message-ID: <fb7c14c5-0aaf-6f90-caac-71d6ce6f25ae@linux.intel.com> (raw)
In-Reply-To: <353d1dc7e3c4e9b5f127ac9177a863d8a8cde39f.camel@linux.ibm.com>
On Wed, 20 Aug 2025, Gerd Bayer wrote:
> On Wed, 2025-08-13 at 22:45 +0800, Hans Zhang wrote:
> > Refactor the __pci_find_next_cap_ttl() to improve code clarity:
> > - Replace magic number 0x40 with PCI_STD_HEADER_SIZEOF.
> > - Use ALIGN_DOWN() for position alignment instead of manual bitmask.
> > - Extract PCI capability fields via FIELD_GET() with standardized masks.
> > - Add necessary headers (linux/align.h).
> >
> > No functional changes intended.
> >
> > Signed-off-by: Hans Zhang <18255117159@163.com>
> > Acked-by: Manivannan Sadhasivam <mani@kernel.org>
> > ---
> > drivers/pci/pci.c | 9 +++++----
> > include/uapi/linux/pci_regs.h | 3 +++
> > 2 files changed, 8 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> > index b0f4d98036cd..40a5c87d9a6b 100644
> > --- a/drivers/pci/pci.c
> > +++ b/drivers/pci/pci.c
> > @@ -9,6 +9,7 @@
> > */
> >
> > #include <linux/acpi.h>
> > +#include <linux/align.h>
> > #include <linux/kernel.h>
> > #include <linux/delay.h>
> > #include <linux/dmi.h>
> > @@ -432,17 +433,17 @@ static u8 __pci_find_next_cap_ttl(struct pci_bus *bus, unsigned int devfn,
> > pci_bus_read_config_byte(bus, devfn, pos, &pos);
> >
> > while ((*ttl)--) {
> > - if (pos < 0x40)
> > + if (pos < PCI_STD_HEADER_SIZEOF)
> > break;
> > - pos &= ~3;
> > + pos = ALIGN_DOWN(pos, 4);
> > pci_bus_read_config_word(bus, devfn, pos, &ent);
> >
> > - id = ent & 0xff;
> > + id = FIELD_GET(PCI_CAP_ID_MASK, ent);
> > if (id == 0xff)
> > break;
> > if (id == cap)
> > return pos;
> > - pos = (ent >> 8);
> > + pos = FIELD_GET(PCI_CAP_LIST_NEXT_MASK, ent);
> > }
> > return 0;
> > }
> > diff --git a/include/uapi/linux/pci_regs.h b/include/uapi/linux/pci_regs.h
> > index f5b17745de60..1bba99b46227 100644
> > --- a/include/uapi/linux/pci_regs.h
> > +++ b/include/uapi/linux/pci_regs.h
> > @@ -207,6 +207,9 @@
> >
> > /* Capability lists */
> >
> > +#define PCI_CAP_ID_MASK 0x00ff /* Capability ID mask */
> > +#define PCI_CAP_LIST_NEXT_MASK 0xff00 /* Next Capability Pointer mask */
> > +
> > #define PCI_CAP_LIST_ID 0 /* Capability ID */
> > #define PCI_CAP_ID_PM 0x01 /* Power Management */
> > #define PCI_CAP_ID_AGP 0x02 /* Accelerated Graphics Port */
>
> Hi Hans,
>
> I like your approach to replace the magic numbers here. If you went
> further to replace the single pci_bus_read_config_word() with two
> single-byte reads at the appropriate places - for CAP_ID and
> CAP_LIST_NEXT - you could even go with the already existing offset
> defines PCI_CAP_LIST_ID and PCI_CAP_LIST_NEXT from pci_regs.h.
>
> But that might be a more intricate change and involves more HW accesses
> than what it's worth.
Hi,
As you noted, it'll be less efficient so it's undesirable to split the
read.
It's somewhat problematic that some of the defines in
include/uapi/linux/pci_regs.h cannot be easily used efficiently with
multi-byte reads leading to use of literals in code.
IMO, adding the multi-byte masks like this Hans' change is IMO the correct
way to address it.
> So feel free to add my
> Reviewed-by: Gerd Bayer <gbayer@linux.ibm.com>
>
> Thanks,
> Gerd
>
--
i.
next prev parent reply other threads:[~2025-08-20 11:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 14:45 [PATCH v15 0/6] Refactor capability search into common macros Hans Zhang
2025-08-13 14:45 ` [PATCH v15 1/6] PCI: Clean up __pci_find_next_cap_ttl() readability Hans Zhang
2025-08-20 9:19 ` Gerd Bayer
2025-08-20 11:36 ` Ilpo Järvinen [this message]
2025-08-13 14:45 ` [PATCH v15 2/6] PCI: Refactor capability search into PCI_FIND_NEXT_CAP() Hans Zhang
2025-08-13 14:45 ` [PATCH v15 3/6] PCI: Refactor extended capability search into PCI_FIND_NEXT_EXT_CAP() Hans Zhang
2025-08-13 14:45 ` [PATCH v15 4/6] PCI: dwc: Use PCI core APIs to find capabilities Hans Zhang
2025-08-13 14:45 ` [PATCH v15 5/6] PCI: cadence: " Hans Zhang
2025-08-13 14:45 ` [PATCH v15 6/6] PCI: cadence: Use cdns_pcie_find_*capability() to avoid hardcoding offsets Hans Zhang
2025-08-14 8:32 ` [PATCH v15 0/6] Refactor capability search into common macros Niklas Schnelle
2025-08-14 14:51 ` Hans Zhang
2025-08-14 20:25 ` Bjorn Helgaas
2025-08-14 20:37 ` Niklas Schnelle
2025-08-14 20:51 ` Bjorn Helgaas
2025-08-14 22:21 ` Hans Zhang
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=fb7c14c5-0aaf-6f90-caac-71d6ce6f25ae@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=18255117159@163.com \
--cc=arnd@kernel.org \
--cc=bhelgaas@google.com \
--cc=gbayer@linux.ibm.com \
--cc=geert@linux-m68k.org \
--cc=helgaas@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=lukas@wunner.de \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=schnelle@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).