From: Douglas Raillard <douglas.raillard@arm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] sched/cpufreq: Align trace event behavior of fast switching
Date: Thu, 8 Aug 2019 17:18:00 +0100 [thread overview]
Message-ID: <433793e3-14c4-9f3b-d503-76471a98b0af@arm.com> (raw)
In-Reply-To: <CAJZ5v0gqqoOzjUMhUgqKzaj8tCegddJphr+MHj5HD2_VAc1QYQ@mail.gmail.com>
Hi Rafael,
On 8/7/19 9:40 PM, Rafael J. Wysocki wrote:
> On Wed, Aug 7, 2019 at 5:34 PM Douglas RAILLARD
> <douglas.raillard@arm.com> wrote:
>>
>> Fast switching path only emits an event for the CPU of interest, whereas the
>> regular path emits an event for all the CPUs that had their frequency changed,
>> i.e. all the CPUs sharing the same policy.
>>
>> With the current behavior, looking at cpu_frequency event for a given CPU that
>> is using the fast switching path will not give the correct frequency signal.
>
> Do you actually have any systems where that is a problem? If so, then
> what are they?
>
That happens on Google Pixel 3 smartphone, which uses this cpufreq driver: drivers/cpufreq/qcom-cpufreq-hw.c.
[1] git clone https://git.linaro.org/people/amit.pundir/linux.git -b blueline-mainline-tracking
Thanks,
Douglas
next prev parent reply other threads:[~2019-08-08 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 15:33 [PATCH] sched/cpufreq: Align trace event behavior of fast switching Douglas RAILLARD
2019-08-07 20:40 ` Rafael J. Wysocki
2019-08-08 16:18 ` Douglas Raillard [this message]
2019-08-26 9:10 ` Rafael J. Wysocki
2019-08-26 9:40 ` Peter Zijlstra
2019-08-26 9:51 ` Dietmar Eggemann
2019-08-26 11:24 ` Peter Zijlstra
2019-08-26 12:12 ` Dietmar Eggemann
2019-08-28 9:44 ` 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=433793e3-14c4-9f3b-d503-76471a98b0af@arm.com \
--to=douglas.raillard@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@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