From: Amit Kucheria <amit.kucheria@verdurent.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"open list:POWER MANAGEMENT CORE" <linux-pm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/4] powercap/drivers/idle_inject: Specify idle state max latency
Date: Wed, 6 May 2020 15:26:58 +0530 [thread overview]
Message-ID: <CAHLCerPZ-VMWmEDXqYRka8sWnVnnmJRSLhwG-zm_0Th3ZwzBqA@mail.gmail.com> (raw)
In-Reply-To: <20200429103644.5492-1-daniel.lezcano@linaro.org>
On Wed, Apr 29, 2020 at 4:07 PM Daniel Lezcano
<daniel.lezcano@linaro.org> wrote:
>
> Currently the idle injection framework uses the play_idle() function
> which puts the current CPU in an idle state. The idle state is the
> deepest one, as specified by the latency constraint when calling the
> subsequent play_idle_precise() function with the INT_MAX.
>
> The idle_injection is used by the cpuidle_cooling device which
> computes the idle / run duration to mitigate the temperature by
> injecting idle cycles. The cooling device has no control on the depth
> of the idle state.
>
> Allow finer control of the idle injection mechanism by allowing to
> specify the latency for the idle state. Thus the cooling device has
> the ability to have a guarantee on the exit latency of the idle states
> it is injecting.
>
> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Reviewed-by: Amit Kucheria <amit.kucheria@linaro.org>
> ---
> - V4:
> - Respin against v5.7-rc1
> ---
> drivers/powercap/idle_inject.c | 16 +++++++++++++++-
> include/linux/idle_inject.h | 4 ++++
> 2 files changed, 19 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/powercap/idle_inject.c b/drivers/powercap/idle_inject.c
> index e9bbd3c42eef..c90f0990968b 100644
> --- a/drivers/powercap/idle_inject.c
> +++ b/drivers/powercap/idle_inject.c
> @@ -61,12 +61,14 @@ struct idle_inject_thread {
> * @timer: idle injection period timer
> * @idle_duration_us: duration of CPU idle time to inject
> * @run_duration_us: duration of CPU run time to allow
> + * @latency_us: max allowed latency
> * @cpumask: mask of CPUs affected by idle injection
> */
> struct idle_inject_device {
> struct hrtimer timer;
> unsigned int idle_duration_us;
> unsigned int run_duration_us;
> + unsigned int latency_us;
> unsigned long cpumask[];
> };
>
> @@ -138,7 +140,8 @@ static void idle_inject_fn(unsigned int cpu)
> */
> iit->should_run = 0;
>
> - play_idle(READ_ONCE(ii_dev->idle_duration_us));
> + play_idle_precise(READ_ONCE(ii_dev->idle_duration_us) * NSEC_PER_USEC,
> + READ_ONCE(ii_dev->latency_us) * NSEC_PER_USEC);
> }
>
> /**
> @@ -169,6 +172,16 @@ void idle_inject_get_duration(struct idle_inject_device *ii_dev,
> *idle_duration_us = READ_ONCE(ii_dev->idle_duration_us);
> }
>
> +/**
> + * idle_inject_set_latency - set the maximum latency allowed
> + * @latency_us: set the latency requirement for the idle state
> + */
> +void idle_inject_set_latency(struct idle_inject_device *ii_dev,
> + unsigned int latency_us)
> +{
> + WRITE_ONCE(ii_dev->latency_us, latency_us);
> +}
> +
> /**
> * idle_inject_start - start idle injections
> * @ii_dev: idle injection control device structure
> @@ -297,6 +310,7 @@ struct idle_inject_device *idle_inject_register(struct cpumask *cpumask)
> cpumask_copy(to_cpumask(ii_dev->cpumask), cpumask);
> hrtimer_init(&ii_dev->timer, CLOCK_MONOTONIC, HRTIMER_MODE_REL);
> ii_dev->timer.function = idle_inject_timer_fn;
> + ii_dev->latency_us = UINT_MAX;
>
> for_each_cpu(cpu, to_cpumask(ii_dev->cpumask)) {
>
> diff --git a/include/linux/idle_inject.h b/include/linux/idle_inject.h
> index a445cd1a36c5..91a8612b8bf9 100644
> --- a/include/linux/idle_inject.h
> +++ b/include/linux/idle_inject.h
> @@ -26,4 +26,8 @@ void idle_inject_set_duration(struct idle_inject_device *ii_dev,
> void idle_inject_get_duration(struct idle_inject_device *ii_dev,
> unsigned int *run_duration_us,
> unsigned int *idle_duration_us);
> +
> +void idle_inject_set_latency(struct idle_inject_device *ii_dev,
> + unsigned int latency_ns);
> +
> #endif /* __IDLE_INJECT_H__ */
> --
> 2.17.1
>
prev parent reply other threads:[~2020-05-06 9:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 10:36 [PATCH v4 1/4] powercap/drivers/idle_inject: Specify idle state max latency Daniel Lezcano
2020-04-29 10:36 ` [PATCH v4 2/4] dt-bindings: thermal: Add the idle cooling device Daniel Lezcano
2020-05-06 9:57 ` Amit Kucheria
2020-04-29 10:36 ` [PATCH v4 3/4] thermal/drivers/cpuidle_cooling: Change the registration function Daniel Lezcano
2020-04-29 20:00 ` Lukasz Luba
2020-05-06 9:57 ` Amit Kucheria
2020-04-29 10:36 ` [PATCH v4 4/4] thermal: cpuidle: Register cpuidle cooling device Daniel Lezcano
2020-04-29 20:02 ` Lukasz Luba
2020-04-29 21:01 ` Daniel Lezcano
2020-05-04 18:00 ` Daniel Lezcano
2020-05-15 9:58 ` Sudeep Holla
2020-05-15 11:03 ` Daniel Lezcano
2020-05-06 9:57 ` Amit Kucheria
2020-06-15 11:25 ` Ulf Hansson
2020-05-06 9:56 ` Amit Kucheria [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=CAHLCerPZ-VMWmEDXqYRka8sWnVnnmJRSLhwG-zm_0Th3ZwzBqA@mail.gmail.com \
--to=amit.kucheria@verdurent.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@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 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).