From: Giovanni Gherdovich <ggherdovich@suse.cz>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Quentin Perret <qperret@qperret.net>,
srinivas.pandruvada@linux.intel.com, tglx@linutronix.de,
mingo@redhat.com, bp@suse.de, lenb@kernel.org, rjw@rjwysocki.net,
x86@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, mgorman@techsingularity.net,
matt@codeblueprint.co.uk, viresh.kumar@linaro.org,
juri.lelli@redhat.com, pjt@google.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com
Subject: Re: [PATCH 1/2] x86,sched: Add support for frequency invariance
Date: Wed, 02 Oct 2019 14:27:54 +0200 [thread overview]
Message-ID: <1570019274.22393.2.camel@suse.cz> (raw)
In-Reply-To: <20190924160022.GB2386@hirez.programming.kicks-ass.net>
On Tue, 2019-09-24 at 18:00 +0200, Peter Zijlstra wrote:
> On Tue, Sep 24, 2019 at 04:03:32PM +0200, Peter Zijlstra wrote:
>
> > > I'll check what's the cost of static_cpu_has() and if it's non-negligible I'll
> > > do what you suggest (x86-specific version of arch_scale_freq_invariant().
> >
> > static_cpu_has() is an alternative and ends up being a static branch
> > (similar to static_key) once the alternative patching runs.
>
> That said; I think you want a static key anyway, because if we can't
> tell the max_freq we don't want to use the invariant stuff.
>
> Something a little like so on top perhaps.
>
> Also, the below fixes that silly tick_disable stuff.
Thanks for this patch, I'll add this change in v2.
Can you elaborate on what you don't like in the tick_disable mechanism?
After reading your comments I realized there is a problem, but I'm not sure is
the same you're addressing.
More on this below, under your edit of the function
x86_arch_scale_freq_tick_disable().
>
> ---
> --- a/arch/x86/include/asm/topology.h
> +++ b/arch/x86/include/asm/topology.h
> @@ -196,20 +196,24 @@ static inline void sched_clear_itmt_supp
> #ifdef CONFIG_SMP
> #include <asm/cpufeature.h>
>
> -#define arch_scale_freq_tick arch_scale_freq_tick
> -#define arch_scale_freq_capacity arch_scale_freq_capacity
> +DECLARE_STATIC_KEY_FALSE(arch_scale_freq_key);
> +
> +#define arch_scale_freq_invariant() static_branch_likely(&arch_scale_freq_key)
This confused me for a second but then I realized that this #define comes
before the one in kernel/sched/sched.h where arch_scale_freq_invariant() is
defined again but guarded against previous definitions, so it all falls into
place; code from schedutil will see this one.
>
> DECLARE_PER_CPU(unsigned long, arch_cpu_freq);
>
> static inline long arch_scale_freq_capacity(int cpu)
> {
> - if (static_cpu_has(X86_FEATURE_APERFMPERF))
> + if (arch_scale_freq_invariant())
> return per_cpu(arch_cpu_freq, cpu);
>
> return 1024 /* SCHED_CAPACITY_SCALE */;
> }
> +#define arch_scale_freq_capacity arch_scale_freq_capacity
>
> extern void arch_scale_freq_tick(void);
> +#define arch_scale_freq_tick arch_scale_freq_tick
> +
> extern void x86_arch_scale_freq_tick_enable(void);
> extern void x86_arch_scale_freq_tick_disable(void);
> #else
> --- a/arch/x86/kernel/smpboot.c
> +++ b/arch/x86/kernel/smpboot.c
> @@ -1799,6 +1799,8 @@ void native_play_dead(void)
> * freq_curr / freq_max to eventually grow >1, in which case we clip it to 1.
> */
>
> +DEFINE_STATIC_KEY_FALSE(arch_scale_freq_key);
> +
> static DEFINE_PER_CPU(u64, arch_prev_aperf);
> static DEFINE_PER_CPU(u64, arch_prev_mperf);
> static u64 arch_max_freq = SCHED_CAPACITY_SCALE;
> @@ -1860,6 +1862,8 @@ static void core_set_cpu_max_freq(void)
> turbo_ratio = (turbo_ratio >> 24) & 0xFF; /* 4C turbo ratio */
>
> arch_max_freq = div_u64(turbo_ratio * SCHED_CAPACITY_SCALE, ratio);
> +
> + static_key_enable(&arch_scale_freq_key);
> }
>
> static void intel_set_cpu_max_freq(void)
> @@ -1876,10 +1880,19 @@ static void intel_set_cpu_max_freq(void)
> core_set_cpu_max_freq();
> }
>
> -static void set_cpu_max_freq(void)
> +static void init_scale_freq(void *arg)
> {
> u64 aperf, mperf;
>
> + rdmsrl(MSR_IA32_APERF, aperf);
> + rdmsrl(MSR_IA32_MPERF, mperf);
> +
> + this_cpu_write(arch_prev_aperf, aperf);
> + this_cpu_write(arch_prev_mperf, mperf);
> +}
> +
> +static void set_cpu_max_freq(void)
> +{
> if (!boot_cpu_has(X86_FEATURE_APERFMPERF))
> return;
>
> @@ -1891,11 +1904,7 @@ static void set_cpu_max_freq(void)
> break;
> }
>
> - rdmsrl(MSR_IA32_APERF, aperf);
> - rdmsrl(MSR_IA32_MPERF, mperf);
> -
> - this_cpu_write(arch_prev_aperf, aperf);
> - this_cpu_write(arch_prev_mperf, mperf);
> + init_scale_freq(NULL);
> }
>
> DEFINE_PER_CPU(unsigned long, arch_cpu_freq);
> @@ -1908,7 +1917,7 @@ void arch_scale_freq_tick(void)
> u64 aperf, mperf;
> u64 acnt, mcnt;
>
> - if (!static_cpu_has(X86_FEATURE_APERFMPERF) || tick_disable)
> + if (!arch_scale_freq_invariant() || tick_disable)
> return;
>
> rdmsrl(MSR_IA32_APERF, aperf);
> @@ -1940,5 +1949,6 @@ void x86_arch_scale_freq_tick_enable(voi
>
> void x86_arch_scale_freq_tick_disable(void)
> {
> + on_each_cpu(init_scale_freq, NULL, 1);
> tick_disable = true;
I don't see why the call init_scale_freq() here is needed; why would I care of
what's in arch_prev_[am]perf at this point. arch_scale_freq_tick() will see
that tick_disable == true and exit early before reading arch_prev_[am]perf.
The problem IMO emerges in the following configuration, which is a bug in the
patch I sent:
* arch_scale_freq_invariant() is true (because we have APERF/MPERF)
* arch_scale_freq_capacity() is non-trivial (reads arch_cpu_freq)
* tick calculations are disabled
In this case arch_scale_freq_capacity() feeds stale data to the function
update_rq_clock_pelt() in kernel/sched/pelt.h. I initially missed this problem
because I forgot that PELT signals have more users than just the schedutil
governor (load balancer etc).
This is exactly the situation produced by patch 2/2 which disables the tick
calculations for intel_cpufreq (aka intel_pstate=passive).
I think the fix for this is to set arch_cpu_freq (each per-cpu instance of the
variable) to SCHED_CAPACITY_SCALE here in x86_arch_scale_freq_tick_disable().
That would render the scaling factor for invariance moot (always 1), just as
it is w/o scale invariance.
I'm sending v2 with all your amendmends except this last one.
Giovanni
next prev parent reply other threads:[~2019-10-02 12:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 2:42 [PATCH 0/2] Add support for frequency invariance for (some) x86 Giovanni Gherdovich
2019-09-09 2:42 ` [PATCH 1/2] x86,sched: Add support for frequency invariance Giovanni Gherdovich
2019-09-11 15:28 ` Doug Smythies
2019-09-13 20:58 ` Doug Smythies
2019-09-17 14:25 ` Giovanni Gherdovich
2019-09-19 14:42 ` Doug Smythies
2019-09-24 8:06 ` Mel Gorman
2019-09-24 17:52 ` Doug Smythies
2019-09-13 22:52 ` Srinivas Pandruvada
2019-09-17 14:27 ` Giovanni Gherdovich
2019-09-17 15:55 ` Vincent Guittot
2019-09-19 23:55 ` Srinivas Pandruvada
2019-09-14 10:57 ` Quentin Perret
2019-09-17 14:27 ` Giovanni Gherdovich
2019-09-17 14:39 ` Quentin Perret
2019-09-24 14:03 ` Peter Zijlstra
2019-09-24 16:00 ` Peter Zijlstra
2019-10-02 12:27 ` Giovanni Gherdovich [this message]
2019-10-02 18:45 ` Peter Zijlstra
2019-09-24 16:04 ` Peter Zijlstra
2019-10-02 12:26 ` Giovanni Gherdovich
2019-10-02 18:35 ` Peter Zijlstra
2019-09-24 16:30 ` Peter Zijlstra
2019-10-02 12:25 ` Giovanni Gherdovich
2019-10-02 18:47 ` Peter Zijlstra
2019-09-09 2:42 ` [PATCH 2/2] cpufreq: intel_pstate: Conditional frequency invariant accounting Giovanni Gherdovich
2019-09-24 16:01 ` [PATCH 0/2] Add support for frequency invariance for (some) x86 Peter Zijlstra
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=1570019274.22393.2.camel@suse.cz \
--to=ggherdovich@suse.cz \
--cc=bp@suse.de \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=qperret@qperret.net \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=x86@kernel.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).