From: "Doug Smythies" <dsmythies@telus.net>
To: "'Rafael J. Wysocki'" <rjw@rjwysocki.net>
Cc: "'LKML'" <linux-kernel@vger.kernel.org>,
"'Leo Yan'" <leo.yan@linaro.org>,
"'Daniel Lezcano'" <daniel.lezcano@linaro.org>,
"'Frederic Weisbecker'" <frederic@kernel.org>,
"'Linux PM'" <linux-pm@vger.kernel.org>,
"'Peter Zijlstra'" <peterz@infradead.org>,
"Doug Smythies" <dsmythies@telus.net>
Subject: RE: [PATCH] cpuidle: menu: Retain tick when shallow state is selected
Date: Fri, 24 Aug 2018 08:44:35 -0700 [thread overview]
Message-ID: <000701d43bc1$5e0c2c50$1a2484f0$@net> (raw)
In-Reply-To: t8fgfrW4IttF2t8fhf7XeN
On 2018.08.24 02:44 Rafael J. Wysocki wrote:
> On Tuesday, August 21, 2018 10:44:10 AM CEST Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>>
>> The case addressed by commit 5ef499cd571c (cpuidle: menu: Handle
>> stopped tick more aggressively) in the stopped tick case is present
>> when the tick has not been stopped yet too.
... [snip] ...
>> Fixes: 87c9fe6ee495 (cpuidle: menu: Avoid selecting shallow states with stopped tick)
... [snip] ...
> Due to the lack of objections, I'm inclined to queue this up.
I have been following these threads.
Recall that I was involved, over a period of months, in the original
"powernightmare" stuff.
I have revived my tests (and wish I had left myself better notes), and
am establishing a baseline before adding and trying this patch.
My baseline is actually two tests with and without the previous two patches (the ones
that were just sent a couple of days ago in "More power management updates for v4.19-rc1".
I might have those results in some presentable form by later today (it looks O.K.)
Results with this patch will take another couple of days.
... Doug
next prev parent reply other threads:[~2018-08-24 15:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 8:44 [PATCH] cpuidle: menu: Retain tick when shallow state is selected Rafael J. Wysocki
2018-08-22 12:02 ` leo.yan
2018-08-22 12:03 ` leo.yan
2018-08-22 21:01 ` Rafael J. Wysocki
2018-08-24 9:44 ` Rafael J. Wysocki
2018-08-24 15:44 ` Doug Smythies [this message]
2018-08-25 11:21 ` Rafael J. Wysocki
2018-08-26 19:37 ` Doug Smythies
2018-08-29 4:19 ` Rafael J. Wysocki
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='000701d43bc1$5e0c2c50$1a2484f0$@net' \
--to=dsmythies@telus.net \
--cc=daniel.lezcano@linaro.org \
--cc=frederic@kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
/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).