From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Tuukka Tikkanen <tuukka.tikkanen@linaro.org>,
linux-pm@vger.kernel.org, rjw@rjwysocki.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/7] Cpuidle: poll state can measure residency
Date: Tue, 25 Feb 2014 11:56:39 +0100 [thread overview]
Message-ID: <530C76E7.8090607@linaro.org> (raw)
In-Reply-To: <1393223377-5744-8-git-send-email-tuukka.tikkanen@linaro.org>
On 02/24/2014 07:29 AM, Tuukka Tikkanen wrote:
> For some platforms, a poll state is inserted in the cpuidle driver states.
> The flags for the state do not indicate that timekeeping is not affected.
> As the state does not do anything apart from calling cpu_relax(), the
> times returned by ktime_get should remain valid. Add the missing flag.
Yes, but it is done with the interrupt enabled, so the interrupt handler
+ softirq handler times will be accounted in the residency time.
I am not sure adding this flag is good.
> Signed-off-by: Tuukka Tikkanen <tuukka.tikkanen@linaro.org>
> ---
> drivers/cpuidle/driver.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpuidle/driver.c b/drivers/cpuidle/driver.c
> index 06dbe7c..136d6a2 100644
> --- a/drivers/cpuidle/driver.c
> +++ b/drivers/cpuidle/driver.c
> @@ -209,7 +209,7 @@ static void poll_idle_init(struct cpuidle_driver *drv)
> state->exit_latency = 0;
> state->target_residency = 0;
> state->power_usage = -1;
> - state->flags = 0;
> + state->flags = CPUIDLE_FLAG_TIME_VALID;
> state->enter = poll_idle;
> state->disabled = false;
> }
>
--
<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
next prev parent reply other threads:[~2014-02-25 10:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 6:29 [PATCH 0/7] Cpuidle: Minor fixes Tuukka Tikkanen
2014-02-24 6:29 ` [PATCH 1/7] Cpuidle: rename expected_us to next_timer_us in menu governor Tuukka Tikkanen
2014-02-24 16:52 ` Nicolas Pitre
2014-03-05 22:26 ` Len Brown
2014-02-24 6:29 ` [PATCH 2/7] Cpuidle: Use actual state latency " Tuukka Tikkanen
2014-02-24 22:35 ` Daniel Lezcano
2014-02-24 6:29 ` [PATCH 3/7] Cpuidle: Ensure menu coefficients stay within domain Tuukka Tikkanen
2014-02-24 16:57 ` Nicolas Pitre
2014-02-24 6:29 ` [PATCH 4/7] Cpuidle: Do not substract exit latency from assumed sleep length Tuukka Tikkanen
2014-02-24 6:29 ` [PATCH 5/7] Cpuidle: Move perf multiplier calculation out of the selection loop Tuukka Tikkanen
2014-02-24 6:29 ` [PATCH 6/7] Cpuidle: Deal with timer expiring in the past Tuukka Tikkanen
2014-02-24 17:05 ` Nicolas Pitre
2014-02-25 0:20 ` Rafael J. Wysocki
2014-03-06 7:41 ` Len Brown
2014-03-07 3:09 ` Len Brown
2014-03-10 10:54 ` Tuukka Tikkanen
2014-03-21 23:10 ` Len Brown
2014-02-24 6:29 ` [PATCH 7/7] Cpuidle: poll state can measure residency Tuukka Tikkanen
2014-02-25 10:56 ` Daniel Lezcano [this message]
2014-02-25 15:40 ` Tuukka Tikkanen
2014-02-24 21:24 ` [PATCH 0/7] Cpuidle: Minor fixes Daniel Lezcano
2014-02-26 0:46 ` Rafael J. Wysocki
2014-03-07 12:12 ` Rafael J. Wysocki
2014-03-11 19:35 ` Rik van Riel
2014-03-11 20:07 ` Rafael J. Wysocki
2014-03-11 21:06 ` Rik van Riel
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=530C76E7.8090607@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tuukka.tikkanen@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).