From: "Doug Smythies" <dsmythies@telus.net>
To: "'Rafael J. Wysocki'" <rjw@rjwysocki.net>
Cc: "'Linux Documentation'" <linux-doc@vger.kernel.org>,
"'LKML'" <linux-kernel@vger.kernel.org>,
"'Peter Zijlstra'" <peterz@infradead.org>,
"'Srinivas Pandruvada'" <srinivas.pandruvada@linux.intel.com>,
"'Giovanni Gherdovich'" <ggherdovich@suse.cz>,
"'Francisco Jerez'" <francisco.jerez.plata@intel.com>,
"'Viresh Kumar'" <viresh.kumar@linaro.org>,
"'Linux PM'" <linux-pm@vger.kernel.org>
Subject: RE: [PATCH v7] cpufreq: intel_pstate: Implement passive mode with HWP enabled
Date: Sun, 6 Sep 2020 17:16:32 -0700 [thread overview]
Message-ID: <000401d684ac$26ee4880$74cad980$@net> (raw)
In-Reply-To: <000901d674da$4521bda0$cf6538e0$@net>
Hi Rafael,
On 2020.08.17 14:06 Doug Smythies wrote:
> On 2020.08.06 05:04 Rafael J. Wysocki wrote:
>
> > Allow intel_pstate to work in the passive mode with HWP enabled and
> > make it set the HWP minimum performance limit (HWP floor) to the
> > P-state value given by the target frequency supplied by the cpufreq
> > governor, so as to prevent the HWP algorithm and the CPU scheduler
> > from working against each other, at least when the schedutil governor
> > is in use, and update the intel_pstate documentation accordingly.
>
...
>
> powersave governor:
> acpi-cpufreq: good
> intel_cpufreq hwp: bad
> intel_cpufreq no hwp: good
It occurs to me that my expectations as to what
is meant by "powersave" might not agree with yours.
For the powersave governor, this is what we have now:
intel_cpufreq hwp == intel_pstate hwp
intel_cpufreq no hwp == acpi-cpufreq == always minimum freq
intel_pstate no hwp ~= acpi-cpufreq/ondemand
Is that your understanding/intention?
My expectation was/is:
intel_cpufreq hwp == intel_cpufreq no hwp == acpi-cpufreq == always minimum freq
intel_pstate no hwp ~= acpi-cpufreq/ondemand
intel_pstate hwp == Unique. Say, extremely course version of ondemand.
... Doug
prev parent reply other threads:[~2020-09-07 0:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 17:37 [PATCH v2 0/2] cpufreq: intel_pstate: Implement passive mode with HWP enabled Rafael J. Wysocki
2020-07-16 17:38 ` [PATCH v2 1/2] cpufreq: intel_pstate: Rearrange the storing of newv EPP values Rafael J. Wysocki
2020-07-16 17:42 ` [PATCH v2 2/2] cpufreq: intel_pstate: Implement passive mode with HWP enabled Rafael J. Wysocki
2020-07-27 15:13 ` [PATCH v3 0/2] " Rafael J. Wysocki
2020-07-27 15:15 ` [PATCH v3 1/2] cpufreq: intel_pstate: Rearrange the storing of new EPP values Rafael J. Wysocki
2020-07-27 15:17 ` [PATCH v3 2/2] cpufreq: intel_pstate: Implement passive mode with HWP enabled Rafael J. Wysocki
2020-07-28 15:09 ` [PATCH v4 0/2] " Rafael J. Wysocki
2020-07-28 15:11 ` [PATCH v4 1/2] cpufreq: intel_pstate: Rearrange the storing of new EPP values Rafael J. Wysocki
2020-07-30 1:31 ` Francisco Jerez
2020-07-28 15:13 ` [PATCH v4 2/2] cpufreq: intel_pstate: Implement passive mode with HWP enabled Rafael J. Wysocki
2020-08-01 23:21 ` Srinivas Pandruvada
2020-08-02 14:14 ` Doug Smythies
2020-08-02 19:20 ` Srinivas Pandruvada
2020-08-03 17:17 ` [PATCH v5] " Rafael J. Wysocki
2020-08-01 16:39 ` [PATCH v4 0/2] " Srinivas Pandruvada
2020-08-02 14:00 ` Doug Smythies
2020-08-02 18:39 ` Srinivas Pandruvada
2020-08-03 0:26 ` Doug Smythies
2020-08-03 17:23 ` Rafael J. Wysocki
2020-08-04 15:10 ` [PATCH v6] " Rafael J. Wysocki
2020-08-04 17:04 ` Doug Smythies
2020-08-05 9:34 ` Rafael J. Wysocki
2020-08-05 15:38 ` Srinivas Pandruvada
2020-08-05 16:28 ` Rafael J. Wysocki
2020-08-05 16:55 ` [PATCH v7] " Rafael J. Wysocki
2020-08-06 5:55 ` Doug Smythies
2020-08-06 11:25 ` Rafael J. Wysocki
2020-08-06 12:03 ` Rafael J. Wysocki
2020-08-10 0:44 ` Srinivas Pandruvada
2020-08-11 0:51 ` Francisco Jerez
2020-08-11 15:33 ` Rafael J. Wysocki
2020-08-17 21:06 ` Doug Smythies
2020-09-07 0:16 ` Doug Smythies [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='000401d684ac$26ee4880$74cad980$@net' \
--to=dsmythies@telus.net \
--cc=francisco.jerez.plata@intel.com \
--cc=ggherdovich@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).