From: fengchengwen <fengchengwen@huawei.com>
To: Wei Huang <wei.huang2@amd.com>, <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>
Subject: Re: [PATCH RFC 1/3] PCI/TPH: Factor out the ST _DSM evaluation
Date: Thu, 19 Nov 2026 08:18:27 +0800 [thread overview]
Message-ID: <96f7b5bd-2295-42b4-89c5-e548cc1791a9@huawei.com> (raw)
In-Reply-To: <20261001155551.4182899-2-wei.huang2@amd.com>
Acked-by: Chengwen Feng <fengchengwen@huawei.com>
On 10/1/2026 11:55 PM, Wei Huang wrote:
> The ACPI _DSM that returns the CPU to Steering Tag (ST) mapping is
> evaluated in one place today, with the lookup of the ACPI device providing
> it open coded in pcie_tph_get_cpu_st().
>
> Factor the handle lookup and the per-CPU query into tph_dsm_handle() and
> tph_get_cpu_st_info() so other callers can reuse them, name the _DSM
> revision instead of repeating the bare number, and constify the ST info
> passed to tph_extract_tag().
>
> No functional change introduced.
>
> Signed-off-by: Wei Huang <wei.huang2@amd.com>
next prev parent reply other threads:[~2026-11-19 0:18 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-11-19 0:18 ` fengchengwen [this message]
2026-10-01 15:55 ` [PATCH RFC 2/3] PCI: Add per-device debugfs directories Wei Huang
2026-11-19 0:31 ` fengchengwen
2026-10-01 15:55 ` [PATCH RFC 3/3] Expose the CPU/Steering Tag mapping via debugfs Wei Huang
2026-11-19 0:59 ` fengchengwen
2026-11-04 21:32 ` [PATCH RFC 0/3] PCI/TPH: Expose CPU-to-Steering Tag mappings " Wei Huang
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=96f7b5bd-2295-42b4-89c5-e548cc1791a9@huawei.com \
--to=fengchengwen@huawei.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--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 \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox