From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux PM <linux-pm@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Patrick Bellasi <patrick.bellasi@arm.com>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [PATCH v2] cpufreq: schedutil: Trace frequency only if it has changed
Date: Thu, 23 Mar 2017 10:02:13 +0530 [thread overview]
Message-ID: <20170323043213.GC12094@vireshk-i7> (raw)
In-Reply-To: <2563394.lUgF3b60iC@aspire.rjw.lan>
On 22-03-17, 18:32, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> sugov_update_commit() calls trace_cpu_frequency() to record the
> current CPU frequency if it has not changed in the fast switch case
> to prevent utilities from getting confused (they may report that the
> CPU is idle if the frequency has not been recorded for too long, for
> example).
>
> However, that may cause the tracepoint to be triggered quite often
> for no real reason (if the frequency doesn't change, we will not
> modify the last update time stamp and governor computations may
> run again shortly when that happens), so don't do that (arguably, it
> is done to work around a utilities bug anyway).
>
> That allows code duplication in sugov_update_commit() to be reduced
> somewhat too.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
>
> -> v2:
> Drop the trace_cpu_frequency() call in the sg_policy->next_freq == next_freq case.
>
> ---
> kernel/sched/cpufreq_schedutil.c | 16 +++++++---------
> 1 file changed, 7 insertions(+), 9 deletions(-)
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
prev parent reply other threads:[~2017-03-23 4:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 0:56 [PATCH] cpufreq: schedutil: Always trace frequency if it does not change Rafael J. Wysocki
2017-03-22 4:16 ` Viresh Kumar
2017-03-22 9:29 ` Peter Zijlstra
2017-03-22 9:56 ` Viresh Kumar
2017-03-22 12:52 ` Rafael J. Wysocki
2017-03-22 14:05 ` Rafael J. Wysocki
2017-03-22 14:21 ` Peter Zijlstra
2017-03-22 17:13 ` Rafael J. Wysocki
2017-03-22 17:32 ` [PATCH v2] cpufreq: schedutil: Trace frequency only if it has changed Rafael J. Wysocki
2017-03-23 4:32 ` Viresh Kumar [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=20170323043213.GC12094@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patrick.bellasi@arm.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=vincent.guittot@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.