From: sashiko-bot@kernel.org
To: "Wei Huang" <wei.huang2@amd.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH RFC 3/3] Expose the CPU/Steering Tag mapping via debugfs
Date: Thu, 01 Oct 2026 16:04:38 +0000 [thread overview]
Message-ID: <20261001160439.6DD3E1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261001155551.4182899-4-wei.huang2@amd.com>
> Steering Tags (ST) are opaque, platform specific values obtained from the
> ACPI ST _DSM, and are only visible to the driver that asks for them. That
> makes it hard to validate whether firmware reports a sane mapping at all.
>
> Expose the mapping read-only in the debugfs directory of each Root Port
> that has ST _DSM support:
>
> # cat /sys/kernel/debug/pci/0000:00:01.1/tph_cpu_st
> cpu vm_st vm_xst vm_ph_ignore pm_st pm_xst pm_ph_ignore
> 0 0x03 0x0103 0 - - 0
> 1 0x03 0x0103 0 - - 0
>
> Each line holds the raw ST info the _DSM returns for one online CPU;
> invalid tags and failed queries are reported as "-".
>
> The interface is per Root Port because the _DSM is evaluated on the ACPI
> device of the host bridge above it. A system with multiple host bridges may
> return different tags for the same CPU, and the value that matters to a
> driver is the one for the Root Port its device sits below. Root Ports below
> the same host bridge report identical contents.
>
> The file is created during enumeration and removed with the device's
> debugfs directory in pci_destroy_dev(), which returns only once no read is
> running, so the pci_dev the file refers to stays valid.
>
> Signed-off-by: Wei Huang <wei.huang2@amd.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261001155551.4182899-1-wei.huang2@amd.com?part=3
prev parent reply other threads:[~2026-10-01 16:04 UTC|newest]
Thread overview: 7+ 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 [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=20261001160439.6DD3E1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wei.huang2@amd.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 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.