From: "Gautham R. Shenoy" <gautham.shenoy@amd.com>
To: "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>
Cc: "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>,
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: Fri, 7 Nov 2025 10:12:55 +0530 [thread overview]
Message-ID: <aQ14z1P0I3WLYnEi@BLRRASHENOY1.amd.com> (raw)
In-Reply-To: <1f6c7144-9b4e-4252-b62e-71c348f11827@kernel.org>
On Wed, Nov 05, 2025 at 10:00:25AM -0600, Mario Limonciello (AMD) (kernel.org) wrote:
>
> >
>
> The series looks good to me.
>
> Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
Thank you!
>
> 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?
Good catch! Yes, that too needs to be fixed to for_each_online_cpu().
I will spin a v2 to include that patch and pick up your Reviewed-by
tag for the earlier ones, and also Chris's Tested-by tag for the first
two patches.
--
Thanks and Regards
gautham.
next prev parent reply other threads:[~2025-11-07 4:43 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 ` [PATCH 0/4] ACPI: CPPC: Fixes to limit actions " Mario Limonciello (AMD) (kernel.org)
2025-11-07 4:42 ` Gautham R. Shenoy [this message]
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=aQ14z1P0I3WLYnEi@BLRRASHENOY1.amd.com \
--to=gautham.shenoy@amd.com \
--cc=chris.harris79@gmail.com \
--cc=cuiyunhui@bytedance.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=superm1@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®