From: Kenneth Crudup <kenny@panix.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Christian Loehle <christian.loehle@arm.com>,
lukasz.luba@arm.com,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>
Subject: Re: I think there's an issue with e3f1164fc9e ("PM: EM: Support late CPUs booting and capacity adjustment") if there's "holes" in your CPU topology
Date: Thu, 4 Sep 2025 14:14:15 -0700 [thread overview]
Message-ID: <9c22020a-84d9-492a-9f66-77b03fd81f87@panix.com> (raw)
In-Reply-To: <CAJZ5v0j8PGqHYN-XR=pkBCyvhN9kwUDupeU6MJTJoCbiJv8F7Q@mail.gmail.com>
Tested-by: Kenneth R. Crudup <kenny@panix.com>
On 9/4/25 10:40, Rafael J. Wysocki wrote:
> So AFAICS, this can be addressed by something like the attached patch
> (the majority of changes in it is just moving kerneldoc comments
> around and function renaming).
>
> Since intel_pstate handles capacity updates itself, it can do without
> em_check_capacity_update().
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange
County CA
prev parent reply other threads:[~2025-09-04 21:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 5:53 I think there's an issue with e3f1164fc9e ("PM: EM: Support late CPUs booting and capacity adjustment") if there's "holes" in your CPU topology Kenneth Crudup
2025-08-28 14:56 ` Christian Loehle
2025-08-28 17:42 ` Kenneth Crudup
2025-08-29 10:31 ` Christian Loehle
2025-08-29 16:45 ` Rafael J. Wysocki
2025-09-03 17:19 ` Kenneth Crudup
2025-09-03 17:26 ` Christian Loehle
2025-09-03 18:39 ` Kenneth Crudup
2025-09-03 18:40 ` Rafael J. Wysocki
2025-09-03 18:43 ` Kenneth Crudup
2025-09-03 18:53 ` Rafael J. Wysocki
2025-09-04 17:40 ` Rafael J. Wysocki
2025-09-04 18:27 ` Kenneth Crudup
2025-09-04 21:14 ` Kenneth Crudup [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=9c22020a-84d9-492a-9f66-77b03fd81f87@panix.com \
--to=kenny@panix.com \
--cc=christian.loehle@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.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