From: "Doug Smythies" <dsmythies@telus.net>
To: "'Rafael J. Wysocki'" <rjw@rjwysocki.net>
Cc: "'LKML'" <linux-kernel@vger.kernel.org>,
"'Len Brown'" <len.brown@intel.com>,
"'Srinivas Pandruvada'" <srinivas.pandruvada@linux.intel.com>,
"'Peter Zijlstra'" <peterz@infradead.org>,
"'Giovanni Gherdovich'" <ggherdovich@suse.cz>,
"'Linux PM'" <linux-pm@vger.kernel.org>,
"'Francisco Jerez'" <francisco.jerez.plata@intel.com>
Subject: RE: [RFC/RFT][PATCH] cpufreq: intel_pstate: Work in passive mode with HWP enabled
Date: Mon, 25 May 2020 14:09:51 -0700 [thread overview]
Message-ID: <001101d632d8$d6a01b30$83e05190$@net> (raw)
In-Reply-To: <000801d632a9$6a586c90$3f0945b0$@net>
Hi all,
The INTEL_CPUFREQ_TRANSITION_DELAY_HWP = 20000
test results from this e-mail were incorrect.
The test and graphs are being re-done.
On 2020.05.25 08:30 Doug smythies wrote:
>
> Legend - intel_pstate - powersave graph [2].
>
> What? Why is there such a graph, unrelated to this patch?
> Well, because there is a not yet understood effect.
>
> p_powe_stock : intel_pstate, powersave, stock kernel (5.7-rc6), hwp disabled.
> P_powe_hwp : intel_pstate, powersave, patched kernel (5.7-rc6), DELAY_HWP 5000.
> P_powe_hwp2 : intel_pstate, powersave, patched kernel (5.7-rc6), DELAY_HWP 20000.
>
> Conclusion: ??
>
> Note: That I merely made a stupid mistake is a real possibility.
Yes, that was it. However all DELAY_HWP 20000 tests were bad,
Not just this one.
... Doug
next prev parent reply other threads:[~2020-05-25 21:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 17:15 [RFC/RFT][PATCH] cpufreq: intel_pstate: Work in passive mode with HWP enabled Rafael J. Wysocki
2020-05-25 1:36 ` Francisco Jerez
2020-05-25 13:23 ` Rafael J. Wysocki
2020-05-25 20:57 ` Francisco Jerez
2020-05-26 8:19 ` Rafael J. Wysocki
2020-05-26 15:51 ` Doug Smythies
2020-05-26 17:42 ` Rafael J. Wysocki
2020-05-26 18:29 ` Francisco Jerez
2020-05-25 15:30 ` Doug Smythies
2020-05-25 21:09 ` Doug Smythies [this message]
2020-06-15 6:18 ` Doug Smythies
2020-08-24 14:54 ` Doug Smythies
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='001101d632d8$d6a01b30$83e05190$@net' \
--to=dsmythies@telus.net \
--cc=francisco.jerez.plata@intel.com \
--cc=ggherdovich@suse.cz \
--cc=len.brown@intel.com \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.