From: "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>
To: "Gautham R. Shenoy" <gautham.shenoy@amd.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Yunhui Cui <cuiyunhui@bytedance.com>,
Jeremy Linton <jeremy.linton@arm.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Ionela Voinescu <ionela.voinescu@arm.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Christopher Harris <chris.harris79@gmail.com>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 0/4] ACPI: CPPC: Fixes to limit actions to online CPUs
Date: Wed, 5 Nov 2025 10:00:25 -0600 [thread overview]
Message-ID: <1f6c7144-9b4e-4252-b62e-71c348f11827@kernel.org> (raw)
In-Reply-To: <20251105143851.4251-1-gautham.shenoy@amd.com>
On 11/5/2025 8:38 AM, Gautham R. Shenoy wrote:
> Hello,
>
> Christopher Harris reported a regression between v6.10 to v6.11 that
> the amd-pstate driver failed to load even when the commandline had
> "amd_pstate=passive"
> (https://lore.kernel.org/lkml/CAM+eXpdDT7KjLV0AxEwOLkSJ2QtrsvGvjA2cCHvt1d0k2_C4Cw@mail.gmail.com/)
>
> On debugging the issue it was observed that when the commandline
> contains "nosmt=force", the CPPC code fails when performing certain
> checks such as checking for the presence of preferred cores and
> validity of the _CPC object since it iterates through all "present"
> CPUs while the object state was populated only for "online" CPUs.
>
> This patchset contains fixes to address this issue.
>
> The first two patches in the series address the issue reported by
> Chris.
>
> Patches 3 and 4 harden the code in a couple of more functions which
> iterated through the present CPUs when it is more apt to restrict the
> operations to online CPUs
>
>
>
> Gautham R. Shenoy (4):
> ACPI: CPPC: Detect preferred core availability on online CPUs
> ACPI: CPPC: Check _CPC validity for only the online CPUs
> ACPI: CPPC: Perform fast check switch only for online CPUs
> ACPI: CPPC: Limit perf ctrs in PCC check only to online CPUs
>
> arch/x86/kernel/acpi/cppc.c | 2 +-
> drivers/acpi/cppc_acpi.c | 6 +++---
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
The series looks good to me.
Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
But I would say I noticed we are also using for_each_present_cpu() in
amd-pstate with amd_pstate_change_mode_without_dvr_change().
Should that also get a similar change?
next prev parent reply other threads:[~2025-11-05 16:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 14:38 Gautham R. Shenoy
2025-11-05 14:38 ` [PATCH 1/4] ACPI: CPPC: Detect preferred core availability on " Gautham R. Shenoy
2025-11-05 14:38 ` [PATCH 2/4] ACPI: CPPC: Check _CPC validity for only the " Gautham R. Shenoy
2025-11-05 14:38 ` [PATCH 3/4] ACPI: CPPC: Perform fast check switch only for " Gautham R. Shenoy
2025-11-05 14:38 ` [PATCH 4/4] ACPI: CPPC: Limit perf ctrs in PCC check only to " Gautham R. Shenoy
2025-11-05 16:00 ` Mario Limonciello (AMD) (kernel.org) [this message]
2025-11-07 4:42 ` [PATCH 0/4] ACPI: CPPC: Fixes to limit actions " Gautham R. Shenoy
2025-11-05 21:13 ` Chris H
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=1f6c7144-9b4e-4252-b62e-71c348f11827@kernel.org \
--to=superm1@kernel.org \
--cc=chris.harris79@gmail.com \
--cc=cuiyunhui@bytedance.com \
--cc=gautham.shenoy@amd.com \
--cc=ionela.voinescu@arm.com \
--cc=jeremy.linton@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.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 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®