From: "Doug Smythies" <dsmythies@telus.net>
To: "'Rafael J. Wysocki \(Intel\)'" <rafael@kernel.org>,
"'Zak'" <zakbrightonknight@gmail.com>
Cc: <linux-pm@vger.kernel.org>,
"'Srinivas Pandruvada'" <srinivas.pandruvada@linux.intel.com>,
"'Viresh Kumar'" <viresh.kumar@linaro.org>,
<linux-kernel@vger.kernel.org>,
"Doug Smythies" <dsmythies@telus.net>
Subject: RE: [PATCH] cpufreq: intel_pstate: Restore P-state request on resume without HWP
Date: Wed, 28 Oct 2026 15:28:28 -0700 [thread overview]
Message-ID: <006601dd672b$a7d67f90$f7837eb0$@telus.net> (raw)
In-Reply-To: <CAJZ5v0gvruWF7VhVuLrn4AgV9_n6Ayektrh+jB=eLY79ufw4UA@mail.gmail.com>
On 2026.10.28 08:54 Rafael wrote:
> On Tue, Oct 27, 2026 at 10:46 PM Doug Smythies <dsmythies@telus.net> wrote:
>> On 2026.10.27 Rafael wrote:
>>> On Tue, Oct 27, 2026 at 5:36 PM Doug Smythies <dsmythies@telus.net> wrote:>
>>>> On 2026.10.27 07:37 Zak Brighton Knight wrote:
>>
>> ...
>>
>>>> I confirm your findings and tested your proposed patch. It all worked fine.
>>>> I had not seen Rafaels's reply about a possible race condition until now.
>>>>
>>>> Test computer: i5-10600K, 6 cores, 12 CPUs, HWP disabled.
>>>
>>> Passive or active mode?
>>
>> Apologies for the incomplete report.
>
> No worries.
>
>> Passive mode has the issue. Active mode was fine without the need for the patch.
>
> Thanks for the update.
>
> Please check the patch I've just posted if poss.
Because I had already done so before this email, I tested Zak's V2 patch, and it worked fine.
I tested your (Rafael's) patch and it worked fine.
Tested-by: Doug Smythies <dsmythies@telus.net>
I have not reviewed the code and will not have time to for a few days.
... Doug
next prev parent reply other threads:[~2026-10-28 22:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 14:37 [PATCH] cpufreq: intel_pstate: Restore P-state request on resume without HWP Zak
2026-10-27 15:56 ` Rafael J. Wysocki (Intel)
2026-10-27 16:36 ` Doug Smythies
2026-10-27 20:32 ` Rafael J. Wysocki (Intel)
2026-10-27 21:46 ` Doug Smythies
2026-10-28 15:54 ` Rafael J. Wysocki (Intel)
2026-10-28 22:28 ` Doug Smythies [this message]
2026-10-28 9:46 ` [PATCH v2] " Zak Brighton Knight
2026-10-28 15:52 ` Rafael J. Wysocki (Intel)
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='006601dd672b$a7d67f90$f7837eb0$@telus.net' \
--to=dsmythies@telus.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=viresh.kumar@linaro.org \
--cc=zakbrightonknight@gmail.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