From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: rafael@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, ulf.hansson@linaro.org
Subject: Re: [PATCH V2 1/2] cpuidle: Replace use_deepest_state flag by forced_idle_latency_limit_ns
Date: Wed, 20 Nov 2019 12:32:38 +0100 [thread overview]
Message-ID: <02a0be83-942d-934d-dd78-8b1680324863@linaro.org> (raw)
In-Reply-To: <4032150.Wh8QACBdyO@kreacher>
On 20/11/2019 12:05, Rafael J. Wysocki wrote:
> On Saturday, November 16, 2019 2:16:12 PM CET Daniel Lezcano wrote:
>> We want to specify a latency constraint when choosing an idle state at
>> play_idle time. Instead of duplicating the information in the
>> structure or propagate the latency in the call stack, change the
>> use_deepest_state by forced_latency_limit_ns to introduce this
>> constraint. The idea being that when it is set, idle is forced
>> (i.e. no governors), but there is a latency limit for the state to
>> use.
>>
>> A zero latency constraint means "do not use the deepest idle state
>> path" as the 'use_deepest_state' boolean was used in the
>> cpuidle_idle_call.
>>
>> In addition add the play_idle_precise() function getting a nanosec
>> base latency constraint as parameter. The play_idle() function becomes
>> a wrapper passing an U64_MAX to play_idle_precise().
>>
>> Suggested-by: Rafael J. Wysocki <rafael@kernel.org>
>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>> ---
[ ... ]
> Queued up for 5.5 along with the [2/2], but I have made quite a few changes
> to the patches, so please double check the result in my bleeding-edge branch.
>
> Thanks!
They look good to me.
Thanks
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2019-11-20 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 13:16 [PATCH V2 1/2] cpuidle: Replace use_deepest_state flag by forced_idle_latency_limit_ns Daniel Lezcano
2019-11-16 13:16 ` [PATCH V2 2/2] cpuidle: Use the latency to call find_deepest_idle_state Daniel Lezcano
2019-11-20 11:05 ` [PATCH V2 1/2] cpuidle: Replace use_deepest_state flag by forced_idle_latency_limit_ns Rafael J. Wysocki
2019-11-20 11:32 ` Daniel Lezcano [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=02a0be83-942d-934d-dd78-8b1680324863@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=ulf.hansson@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