mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Linux PM <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V5 1/3] cpuidle: play_idle: Make play_idle more flexible
Date: Tue, 29 Oct 2019 09:32:57 +0100	[thread overview]
Message-ID: <2aadcd27-b32d-89f1-8bb8-76893f007c66@linaro.org> (raw)
In-Reply-To: <CAPDyKFqY0pwuD7U-YbdtwF8HqmZ2TVo3U=wbs50uXpWzTf-4NA@mail.gmail.com>

Hi Ulf,


On 28/10/2019 23:26, Ulf Hansson wrote:
> On Mon, 28 Oct 2019 at 15:34, Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>>
>> The play_idle function has two users, the intel powerclamp and the
>> idle_injection.
>>
>> The idle injection cooling device uses the function via the
>> idle_injection powercap's APIs. Unfortunately, play_idle is currently
>> limited by the idle state depth: by default the deepest idle state is
>> selected. On the ARM[64] platforms, most of the time it is the cluster
>> idle state, the exit latency and the residency can be very high. That
>> reduces the scope of the idle injection usage because the impact on
>> the performances can be very significant.
>>
>> If the idle injection cycles can be done with a shallow state like a
>> retention state, the cooling effect would eventually give similar
>> results than the cpufreq cooling device.
>>
>> In order to prepare the function to receive an idle state parameter,
>> let's replace the 'use_deepest_state' boolean field with 'use_state'
>> and use this value to enter the specific idle state.
>>
>> The current code keeps the default behavior which is go to the deepest
>> idle state.
>>
>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>> Acked-by: Mathieu Poirier <mathieu.poirier@linaro.org>
>> Cc: Ulf Hansson <ulf.hansson@linaro.org>
> 
> This looks good to me! Just a minor nitpick, see more below. If you
> don't like my suggestions, I am fine as is. Therefore:

Thank you very much for reviewing the patches.

I don't have any objection about renaming the variables as you suggest.

Rafael, is it fine the renaming?

> Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>


[ ... ]


-- 
 <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


      reply	other threads:[~2019-10-29  8:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28 14:34 Daniel Lezcano
2019-10-28 14:34 ` [PATCH V5 2/3] cpuidle: play_idle: Specify play_idle with an idle state Daniel Lezcano
2019-10-28 22:26   ` Ulf Hansson
2019-10-28 14:34 ` [PATCH V5 3/3] powercap/drivers/idle_inject: Specify the idle state to inject Daniel Lezcano
2019-10-28 22:26   ` Ulf Hansson
2019-10-28 22:26 ` [PATCH V5 1/3] cpuidle: play_idle: Make play_idle more flexible Ulf Hansson
2019-10-29  8: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=2aadcd27-b32d-89f1-8bb8-76893f007c66@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®