From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "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] powercap/drivers/idle_inject: Specify idle state max latency
Date: Thu, 26 Mar 2020 20:47:30 +0100 [thread overview]
Message-ID: <2d8bcc54-e1f9-3d7b-e31a-8463c28dfecd@linaro.org> (raw)
In-Reply-To: <CAJZ5v0ghHFJCfG5vxE=O6+bD4neyvyF2WD6ASGptBaptm2-5Ow@mail.gmail.com>
On 26/03/2020 20:37, Rafael J. Wysocki wrote:
> On Thu, Mar 26, 2020 at 8:20 PM Daniel Lezcano
> <daniel.lezcano@linaro.org> wrote:
>>
>> On 26/03/2020 20:14, Rafael J. Wysocki wrote:
>>> On Thu, Mar 26, 2020 at 3:48 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.
>>>>
>>>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>>>> --- drivers/powercap/idle_inject.c | 27
>>>> ++++++++++++++++++++++++++- include/linux/idle_inject.h |
>>>> 6 ++++++ 2 files changed, 32 insertions(+), 1 deletion(-)
>>
>> [ ... ]
>>
>>>> + +void idle_inject_set_latency(struct idle_inject_device
>>>> *ii_dev, + unsigned int
>>>> latency_ns); + +unsigned int idle_inject_get_latency(struct
>>>> idle_inject_device *ii_dev); + #endif /* __IDLE_INJECT_H__ */
>>>> --
>>>
>>> I would like to see a user of idle_inject_get_latency() before
>>> this goes in.
>>
>> Do you mean a user for the set/get or the get only? If the
>> latter, there is no user yet I just added it to have an usual
>> get/set helpers, if that hurts, I can resend by removing it. If
>> the former, there is a patch I'm about to send which depends on
>> the 'set'.
>
> So I wouldn't add the "get" thing at all if it has no users.
Ok
> Also it would be better to send this patch along with the other
> one depending on it.
Sure will resend along with the other patches.
--
<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:[~2020-03-26 19:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 14:46 Daniel Lezcano
2020-03-26 19:14 ` Rafael J. Wysocki
2020-03-26 19:20 ` Daniel Lezcano
2020-03-26 19:37 ` Rafael J. Wysocki
2020-03-26 19:47 ` 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=2d8bcc54-e1f9-3d7b-e31a-8463c28dfecd@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 \
/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
Powered by JetHome