From: Wei Huang <wei.huang2@amd.com>
To: bhelgaas@google.com
Cc: linux-pci@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
corbet@lwn.net, rdunlap@infradead.org, fengchengwen@huawei.com
Subject: Re: [PATCH RFC 0/3] PCI/TPH: Expose CPU-to-Steering Tag mappings via debugfs
Date: Wed, 4 Nov 2026 15:32:55 -0600 [thread overview]
Message-ID: <auukh0rUCTC8M7fc@weiserver> (raw)
In-Reply-To: <20261001155551.4182899-1-wei.huang2@amd.com>
Hi Bjorn,
Gentle ping on this patch series. Do you have any feedback, or would you be
comfortable to add this support into PCI TPH?
Thanks,
-Wei
On Thu, Oct 01, 2026 at 10:55:48AM -0500, Wei Huang wrote:
> Add reusable per-device PCI debugfs directories and use them to expose
> the firmware-provided CPU-to-Steering Tag mapping for each Root Port.
> Factor the ACPI _DSM query path for reuse and document the new read-only
> interface.
>
> Wei Huang (3):
> PCI/TPH: Factor out the ST _DSM evaluation
> PCI: Add per-device debugfs directories
> Expose the CPU/Steering Tag mapping via debugfs
>
> Documentation/PCI/tph.rst | 32 ++++++
> drivers/pci/Makefile | 1 +
> drivers/pci/debugfs.c | 60 ++++++++++++
> drivers/pci/pci.h | 12 +++
> drivers/pci/remove.c | 1 +
> drivers/pci/tph.c | 201 ++++++++++++++++++++++++++++++++++----
> include/linux/pci.h | 3 +
> 7 files changed, 290 insertions(+), 20 deletions(-)
> create mode 100644 drivers/pci/debugfs.c
>
> --
> 2.55.0
>
prev parent reply other threads:[~2026-11-04 21:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 15:55 [PATCH RFC 0/3] PCI/TPH: Expose CPU-to-Steering Tag mappings via debugfs Wei Huang
2026-10-01 15:55 ` [PATCH RFC 1/3] PCI/TPH: Factor out the ST _DSM evaluation Wei Huang
2026-10-01 16:02 ` sashiko-bot
2026-10-01 15:55 ` [PATCH RFC 2/3] PCI: Add per-device debugfs directories Wei Huang
2026-10-01 16:10 ` sashiko-bot
2026-10-01 15:55 ` [PATCH RFC 3/3] Expose the CPU/Steering Tag mapping via debugfs Wei Huang
2026-10-01 16:04 ` sashiko-bot
2026-11-04 21:32 ` Wei Huang [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=auukh0rUCTC8M7fc@weiserver \
--to=wei.huang2@amd.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=fengchengwen@huawei.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.