From: Logan Gunthorpe <logang@deltatee.com>
To: Ben Cressey <ben@cressey.dev>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Alex Williamson" <alex@shazbot.org>,
"Wei Wang" <wei.w.wang@hotmail.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Anthony Vardaro (Anthropic)" <me@anthonyvardaro.com>
Subject: Re: [PATCH v2] PCI: Add ID@path device format for pci= parameters
Date: Thu, 12 Nov 2026 20:02:53 -0600 [thread overview]
Message-ID: <1a07c926-d710-4922-a4a1-be235df7c74c@deltatee.com> (raw)
In-Reply-To: <20261111-pci-idpath-selector-v2-1-83ea668e38f0@cressey.dev>
On 2026-11-11 5:36 p.m., Ben Cressey wrote:
> The <pci_dev> grammar shared by pci=resource_alignment=,
> pci=disable_acs_redir= and pci=config_acs= names a device either by
> address, with an optional path, or by ID. When one command line serves
> more than one platform, neither form limits an entry to the intended
> device: an address applies to whatever occupies it on each platform, and
> an ID applies to every instance, such as all Downstream Ports of a
> switch rather than the one that needs different ACS settings.
>
> Accept pci:<vendor>:<device>[:<subvendor>:<subdevice>]@<path>, where
> <path> is the address format, and match only when both halves match. An
> entry written for one platform is then inert on another where that
> address holds a different device. For example,
>
> pci=config_acs=xx111x1@pci:10b5:8749@0000:80:02.0/00.0/08.0
>
> configures ACS on the Downstream Port at that path only if it is a
> PEX 8749 port.
>
> The path goes last since pci_dev_str_match_path() consumes up to the
> next ';'. The IDs are compared first, and the path is parsed only for a
> device that matches them. The <order>@ and <flags>@ prefixes of
> resource_alignment and config_acs are stripped before
> pci_dev_str_match() is called, so the callers are unchanged.
>
> Suggested-by: Wei Wang <wei.w.wang@hotmail.com>
> Signed-off-by: Ben Cressey <ben@cressey.dev>
Looks pretty straightforward and the reasoning all makes sense to me.
Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
prev parent reply other threads:[~2026-11-13 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 23:36 Ben Cressey
2026-11-13 2:02 ` Logan Gunthorpe [this message]
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=1a07c926-d710-4922-a4a1-be235df7c74c@deltatee.com \
--to=logang@deltatee.com \
--cc=alex@shazbot.org \
--cc=ben@cressey.dev \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=jgg@ziepe.ca \
--cc=kwilczynski@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=me@anthonyvardaro.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=wei.w.wang@hotmail.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
all inboxes | Powered by JetHome®