linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	"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>,
	Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH V6 2/3] cpuidle: play_idle: Specify play_idle with an idle state
Date: Sun, 10 Nov 2019 17:49:10 +0100	[thread overview]
Message-ID: <CAJZ5v0hEYPbvbW6SErsd=uPsty9pC-4cLhCt2TiZx=JSVWLdsQ@mail.gmail.com> (raw)
In-Reply-To: <59f10030-cef0-4d75-5135-9d0590385fda@linaro.org>

On Fri, Nov 8, 2019 at 2:33 PM Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>
> On 08/11/2019 11:56, Rafael J. Wysocki wrote:
> > On Fri, Nov 8, 2019 at 11:47 AM Daniel Lezcano
> > <daniel.lezcano@linaro.org> wrote:
> >>
> >> On 08/11/2019 02:20, Rafael J. Wysocki wrote:
> >>> On Wednesday, October 30, 2019 8:51:40 AM CET Daniel Lezcano wrote:
> >>>> Currently, the play_idle function does not allow to tell which idle
> >>>> state we want to go. Improve this by passing the idle state as
> >>>> parameter to the function.
> >>>>
> >>>> Export cpuidle_find_deepest_state() symbol as it is used from the
> >>>> intel_powerclamp driver as a module.
> >>>>
> >>>> There is no functional changes, the cpuidle state is the deepest one.
> >>>>
> >>>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> >>>> Acked-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> >>>> Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
> >>>> ---
> >>>>   V6:
> >>>>    - Change variable name 'state' -> 'index':
> >>>>      https://lkml.org/lkml/2019/10/28/874
> >>>>   V4:
> >>>>    - Add EXPORT_SYMBOL_GPL(cpuidle_find_deepest_state) for the
> >>>>      intel_powerclamp driver when this one is compiled as a module
> >>>>   V3:
> >>>>    - Add missing cpuidle.h header
> >>>> ---
> >>>>  drivers/cpuidle/cpuidle.c                | 1 +
> >>>>  drivers/powercap/idle_inject.c           | 4 +++-
> >>>>  drivers/thermal/intel/intel_powerclamp.c | 4 +++-
> >>>>  include/linux/cpu.h                      | 2 +-
> >>>>  kernel/sched/idle.c                      | 4 ++--
> >>>>  5 files changed, 10 insertions(+), 5 deletions(-)
> >>>>
> >>>> diff --git a/drivers/cpuidle/cpuidle.c b/drivers/cpuidle/cpuidle.c
> >>>> index 18523ea6b11b..b871fc2e8e67 100644
> >>>> --- a/drivers/cpuidle/cpuidle.c
> >>>> +++ b/drivers/cpuidle/cpuidle.c
> >>>> @@ -126,6 +126,7 @@ int cpuidle_find_deepest_state(void)
> >>>>
> >>>>      return find_deepest_state(drv, dev, UINT_MAX, 0, false);
> >>>>  }
> >>>> +EXPORT_SYMBOL_GPL(cpuidle_find_deepest_state);
> >>>
> >>> That doesn't appear to be really necessary to me.
> >>>
> >>>>
> >>>>  #ifdef CONFIG_SUSPEND
> >>>>  static void enter_s2idle_proper(struct cpuidle_driver *drv,
> >>>> diff --git a/drivers/powercap/idle_inject.c b/drivers/powercap/idle_inject.c
> >>>> index cd1270614cc6..233c878cbf46 100644
> >>>> --- a/drivers/powercap/idle_inject.c
> >>>> +++ b/drivers/powercap/idle_inject.c
> >>>> @@ -38,6 +38,7 @@
> >>>>  #define pr_fmt(fmt) "ii_dev: " fmt
> >>>>
> >>>>  #include <linux/cpu.h>
> >>>> +#include <linux/cpuidle.h>
> >>>>  #include <linux/hrtimer.h>
> >>>>  #include <linux/kthread.h>
> >>>>  #include <linux/sched.h>
> >>>> @@ -138,7 +139,8 @@ static void idle_inject_fn(unsigned int cpu)
> >>>>       */
> >>>>      iit->should_run = 0;
> >>>>
> >>>> -    play_idle(READ_ONCE(ii_dev->idle_duration_us));
> >>>> +    play_idle(READ_ONCE(ii_dev->idle_duration_us),
> >>>> +              cpuidle_find_deepest_state());
> >>>
> >>> The next patch changes this again and I'm not sure why this intermediate
> >>> change is useful.
> >>>
> >>>>  }
> >>>>
> >>>>  /**
> >>>> diff --git a/drivers/thermal/intel/intel_powerclamp.c b/drivers/thermal/intel/intel_powerclamp.c
> >>>> index 53216dcbe173..b55786c169ae 100644
> >>>> --- a/drivers/thermal/intel/intel_powerclamp.c
> >>>> +++ b/drivers/thermal/intel/intel_powerclamp.c
> >>>> @@ -29,6 +29,7 @@
> >>>>  #include <linux/delay.h>
> >>>>  #include <linux/kthread.h>
> >>>>  #include <linux/cpu.h>
> >>>> +#include <linux/cpuidle.h>
> >>>>  #include <linux/thermal.h>
> >>>>  #include <linux/slab.h>
> >>>>  #include <linux/tick.h>
> >>>> @@ -430,7 +431,8 @@ static void clamp_idle_injection_func(struct kthread_work *work)
> >>>>      if (should_skip)
> >>>>              goto balance;
> >>>>
> >>>> -    play_idle(jiffies_to_usecs(w_data->duration_jiffies));
> >>>> +    play_idle(jiffies_to_usecs(w_data->duration_jiffies),
> >>>> +              cpuidle_find_deepest_state());
> >>>
> >>> I don't see a reason for changing the code here like this.
> >>>
> >>> What you really need is to have a way to set a limit on the idle
> >>> state exit latency for idle injection on ARM.
> >>
> >> Mmh, yes you are right. The idle state number is part of the internals
> >> of the cpuidle framework while the exit latency is an input (from user
> >> or kernel).
> >>
> >>> For that you can pass the exit latency limit to play_idle(), but then
> >>> you need to change powerclamp to pass UNIT_MAX or similar which is
> >>> ugly, or you can redefine cpuidle_use_deepest_state() to take the
> >>> exit latency limit as the arg (with 0 meaning use_deepest_state == false).
> >>
> >> Should it make sense to just get the resume latency in
> >> cpuidle_use_deepest_state() and pass the value to find_deepest_state()?
> >
> > Yes, I would change cpuidle_use_deepest_state() to take the max exit
> > latency as the arg (maybe with 0 meaning "don't use the deepest state
> > only any more").
>
> Why not simply ?
>
> int cpuidle_find_deepest_state(struct cpuidle_driver *drv,
>                                 struct cpuidle_device *dev)
> {
>         int latency = cpuidle_governor_latency_req(dev->cpu);
>
>         return find_deepest_state(drv, dev, latency_req, 0, false);
> }

Because, AFAICS, that doesn't work for powerclamp.

  reply	other threads:[~2019-11-10 16:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30  7:51 [PATCH V6 1/3] cpuidle: play_idle: Make play_idle more flexible Daniel Lezcano
2019-10-30  7:51 ` [PATCH V6 2/3] cpuidle: play_idle: Specify play_idle with an idle state Daniel Lezcano
2019-11-08  1:20   ` Rafael J. Wysocki
2019-11-08 10:47     ` Daniel Lezcano
2019-11-08 10:56       ` Rafael J. Wysocki
2019-11-08 13:32         ` Daniel Lezcano
2019-11-10 16:49           ` Rafael J. Wysocki [this message]
2019-11-13 12:37     ` Daniel Lezcano
2019-12-05 17:04   ` Martin Kepplinger
2019-12-05 18:02     ` Daniel Lezcano
2019-10-30  7:51 ` [PATCH V6 3/3] powercap/drivers/idle_inject: Specify the idle state to inject Daniel Lezcano
2019-11-08  1:24   ` Rafael J. Wysocki
2019-11-06 18:27 ` [PATCH V6 1/3] cpuidle: play_idle: Make play_idle more flexible Daniel Lezcano
2019-11-08  0:53   ` Rafael J. Wysocki
2019-11-08  1:03 ` 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='CAJZ5v0hEYPbvbW6SErsd=uPsty9pC-4cLhCt2TiZx=JSVWLdsQ@mail.gmail.com' \
    --to=rafael@kernel.org \
    --cc=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;
as well as URLs for NNTP newsgroup(s).