From: "Rafael J. Wysocki" <email@example.com>
To: Lukasz Luba <firstname.lastname@example.org>
Cc: "Rafael J. Wysocki" <email@example.com>,
Linux Kernel Mailing List <firstname.lastname@example.org>,
Daniel Lezcano <email@example.com>,
Linux PM <firstname.lastname@example.org>,
Amit Kucheria <email@example.com>,
"Zhang, Rui" <firstname.lastname@example.org>,
Dietmar Eggemann <email@example.com>,
Chris Redpath <Chris.Redpath@arm.com>,
Beata.Michalska@arm.com, Viresh Kumar <firstname.lastname@example.org>,
"Rafael J. Wysocki" <email@example.com>,
Amit Kachhap <firstname.lastname@example.org>
Subject: Re: [RFC PATCH 3/4] cpufreq: Add Active Stats calls tracking frequency changes
Date: Tue, 22 Jun 2021 16:51:03 +0200 [thread overview]
Message-ID: <CAJZ5v0jiu=HpyGt7JpbFsS3dA1MWp9pi7K+wgP5gh+Xn3Jx9kA@mail.gmail.com> (raw)
On Tue, Jun 22, 2021 at 4:09 PM Lukasz Luba <email@example.com> wrote:
> On 6/22/21 2:51 PM, Rafael J. Wysocki wrote:
> > On Tue, Jun 22, 2021 at 3:42 PM Lukasz Luba <firstname.lastname@example.org> wrote:
> >> On 6/22/21 1:28 PM, Rafael J. Wysocki wrote:
> >>> On Tue, Jun 22, 2021 at 9:59 AM Lukasz Luba <email@example.com> wrote:
> >>>> The Active Stats framework tracks and accounts the activity of the CPU
> >>>> for each performance level. It accounts the real residency, when the CPU
> >>>> was not idle, at a given performance level. This patch adds needed calls
> >>>> which provide the CPU frequency transition events to the Active Stats
> >>>> framework.
> >>>> Signed-off-by: Lukasz Luba <firstname.lastname@example.org>
> >>>> ---
> >>>> drivers/cpufreq/cpufreq.c | 5 +++++
> >>>> 1 file changed, 5 insertions(+)
> >>>> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> >>>> index 802abc925b2a..d79cb9310572 100644
> >>>> --- a/drivers/cpufreq/cpufreq.c
> >>>> +++ b/drivers/cpufreq/cpufreq.c
> >>>> @@ -14,6 +14,7 @@
> >>>> #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
> >>>> +#include <linux/active_stats.h>
> >>>> #include <linux/cpu.h>
> >>>> #include <linux/cpufreq.h>
> >>>> #include <linux/cpu_cooling.h>
> >>>> @@ -387,6 +388,8 @@ static void cpufreq_notify_transition(struct cpufreq_policy *policy,
> >>>> cpufreq_stats_record_transition(policy, freqs->new);
> >>>> policy->cur = freqs->new;
> >>>> +
> >>>> + active_stats_cpu_freq_change(policy->cpu, freqs->new);
> >>>> }
> >>>> }
> >>>> @@ -2085,6 +2088,8 @@ unsigned int cpufreq_driver_fast_switch(struct cpufreq_policy *policy,
> >>>> policy->cpuinfo.max_freq);
> >>>> cpufreq_stats_record_transition(policy, freq);
> >>>> + active_stats_cpu_freq_fast_change(policy->cpu, freq);
> >>>> +
> >>> This is quite a bit of overhead and so why is it needed in addition to
> >>> the code below?
> >> The code below is tracing, which is good for post-processing. We use in
> >> our tool LISA, when we analyze the EAS decision, based on captured
> >> trace data.
> >> This new code is present at run time, so subsystems like our thermal
> >> governor IPA can use it and get better estimation about CPU used power
> >> for any arbitrary period, e.g. 50ms, 100ms, 300ms, ...
> > So can it be made not run when the IPA is not using it?
> I can make a Kconfig for IPA to select this ACTIVE_STATS.
> Also, I can add description that this framework is mostly needed
> for IPA, so don't enable it if you don't use IPA (default is 'n'
> so it shouldn't harm others).
> This Active Stats shouldn't be stopped when thermal zone is switching
> between governors at run time, e.g. IPA -> step_wise -> IPA
> because when IPA is set next time, it might not have correct CPU
> stats (what is the current frequency and for how long it has been
> actively used).
But after a while it will collect enough useful data I suppose?
> Beside, switching governors at run time is not a good idea
> (apart from stress testing them ;) ).
> >>> And pretty much the same goes for the idle loop change. There is
> >>> quite a bit of instrumentation in that code already and it avoids
> >>> adding new locking for a reason. Why is it a good idea to add more
> >>> locking to that code?
> >> This active_stats_cpu_freq_fast_change() doesn't use the locking, it
> >> relies on schedutil lock in .
> > Ah, OK.
> > But it still adds overhead AFAICS.
> Agree, it's an extra code. For platforms which use IPA it's a
> justifiable cost, weighted by better estimation thanks to this calls.
> For other platforms, this framework will be set to default 'n' option.
A general problem with build-time configuration is for distros that
want to ship one kernel binary to run on multiple hardware platforms.
They need to enable those options anyway and then get the full cost on
the platforms that don't need it, but want to use the common binary
Again, please consider making this new code run only when it is needed
even if configured in and if it runs, make it as low-overhead as
next prev parent reply other threads:[~2021-06-22 14:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 7:59 [RFC PATCH 0/4] Introduce Active Stats framework with CPU performance statistics Lukasz Luba
2021-06-22 7:59 ` [RFC PATCH 1/4] PM: Introduce Active Stats framework Lukasz Luba
2021-06-22 7:59 ` [RFC PATCH 2/4] cpuidle: Add Active Stats calls tracking idle entry/exit Lukasz Luba
2021-06-22 12:33 ` Rafael J. Wysocki
2021-06-22 13:58 ` Lukasz Luba
2021-06-22 14:44 ` Rafael J. Wysocki
2021-06-22 15:02 ` Lukasz Luba
2021-06-22 7:59 ` [RFC PATCH 3/4] cpufreq: Add Active Stats calls tracking frequency changes Lukasz Luba
2021-06-22 9:32 ` Viresh Kumar
2021-06-22 11:07 ` Lukasz Luba
2021-06-23 3:15 ` Viresh Kumar
2021-06-23 9:14 ` Lukasz Luba
2021-06-22 12:28 ` Rafael J. Wysocki
2021-06-22 13:42 ` Lukasz Luba
2021-06-22 13:51 ` Rafael J. Wysocki
2021-06-22 14:09 ` Lukasz Luba
2021-06-22 14:51 ` Rafael J. Wysocki [this message]
2021-06-22 14:59 ` Rafael J. Wysocki
2021-06-22 15:10 ` Lukasz Luba
2021-06-22 15:02 ` Lukasz Luba
2021-06-22 7:59 ` [RFC PATCH 4/4] thermal: cpufreq_cooling: Improve power estimation based on Active Stats framework Lukasz Luba
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).