From: Giovanni Gherdovich <email@example.com> To: Srinivas Pandruvada <firstname.lastname@example.org>, Thomas Gleixner <email@example.com>, Ingo Molnar <firstname.lastname@example.org>, Peter Zijlstra <email@example.com>, Borislav Petkov <firstname.lastname@example.org>, Len Brown <email@example.com>, "Rafael J . Wysocki" <firstname.lastname@example.org> Cc: email@example.com, firstname.lastname@example.org, email@example.com, Mel Gorman <firstname.lastname@example.org>, Matt Fleming <email@example.com>, Viresh Kumar <firstname.lastname@example.org>, Juri Lelli <email@example.com>, Paul Turner <firstname.lastname@example.org>, Vincent Guittot <email@example.com>, Quentin Perret <firstname.lastname@example.org>, Dietmar Eggemann <email@example.com>, Doug Smythies <firstname.lastname@example.org>, Giovanni Gherdovich <email@example.com> Subject: [PATCH 0/6] Add support for frequency invariance for (some) x86 Date: Mon, 11 Nov 2019 19:05:43 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) v2 at https://email@example.com/ Changes wrt v2: - Removing the tick_disable mechanism. Frequency scale-invariance isn't just about helping schedutil choose better frequencies, but also providing the scheduler load balancer with better metrics. All users of PELT signals benefit from this feature. The tick_disable patch disabled frequency invariant calculation when a specific driver is in use (intel_pstate in active mode). - static_branch_enable(&arch_scale_freq_key) is now called earlier, right after we learn that X86_FEATURE_APERFMPERF is available. Previously Peter Z. commented "if we can't tell the max_freq we don't want to use the invariant stuff.". I've decided to do it differently: if we can't tell the max_freq, then it's because the CPU encodes max_freq in MSRs in a way this patch doesn't understand, and we assume max_p is the max_freq which seems like a safe bet. As a reminder, max_freq=max_p is encoded by setting arch_max_freq=1024 as default value. I'm open to feedback. - Refactoring the switch case statement in set_cpu_max_freq() as Rafael W. Now the first patch doesn't hint at what the following patch will bring along. - Handling the case were turbo is disabled at runtime and a _PPC ACPI notification is issued, as requested by Rafael W. This happens eg. when some laptop model is disconnected from AC. (Patch #6) - Handling all Intel x86_64 micro-arches. - A note for Srinivas P., who expressed concern for Atoms: on Atom CPUs the max_freq is set to the highest turbo level, as a power-efficiency oriented measure. In this way the ratio curr_freq/max_freq tends to be lower, PELT signals are consequently lower, and schedutil doesn't push too hard on speed. (Patches #4 and #5). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cover Letter from v2: v1 at https://firstname.lastname@example.org/ Changes wrt v1: - add x86-specific implementation of arch_scale_freq_invariant() using a static key that checks for the availability of APERF and MPERF - refer to GOLDMONT_D instead of GOLDMONT_X, according to recent rename - set arch_cpu_freq to 1024 from x86_arch_scale_freq_tick_disable() to prevent PELT from being fed stale data - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cover Letter from v1: This is a resend with of Peter Zijlstra's patch to support frequency scale-invariance on x86 from May 2018 [see 1]. I've added some modifications and included performance test results. If Peter doesn't mind, I'm slapping my name on it :) The changes from Peter's original implementation are: 1) normalizing against the 4-cores turbo level instead or 1-core turbo 2) removing the run-time search for when the above value isn't found in the various Intel MSRs -- the base frequency value is taken in that case. The section "4. KNOWN LIMITATIONS" in the first patch commit message addresses the reason why this approach was dropped back in 2018, and explains that the performance gains outweight that issue. The second patch from Srinivas is taken verbatim from the May 2018 submission as it still applies. I apologies for the length of patch #1 commit message; I've made a table of contents with summaries of each section that should make easier to skim through the content. This submission incorporates the feedback and requests for additional tests received during the presentation made at OSPM 2019 in Pisa three months ago.  https://email@example.com/ Giovanni Gherdovich (6): x86,sched: Add support for frequency invariance x86,sched: Add support for frequency invariance on SKYLAKE_X x86,sched: Add support for frequency invariance on XEON_PHI_KNL/KNM x86,sched: Add support for frequency invariance on ATOM_GOLDMONT* x86,sched: Add support for frequency invariance on ATOM x86: intel_pstate: handle runtime turbo disablement/enablement in freq. invariance arch/x86/include/asm/topology.h | 25 ++++ arch/x86/kernel/smpboot.c | 324 +++++++++++++++++++++++++++++++++++++++- drivers/cpufreq/intel_pstate.c | 1 + kernel/sched/core.c | 1 + kernel/sched/sched.h | 7 + 5 files changed, 357 insertions(+), 1 deletion(-) -- 2.16.4
next reply other threads:[~2019-11-11 18:00 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-11 18:05 Giovanni Gherdovich [this message] 2019-11-11 18:05 ` [PATCH 1/6] x86,sched: Add support for frequency invariance Giovanni Gherdovich 2019-11-11 18:05 ` [PATCH 2/6] x86,sched: Add support for frequency invariance on SKYLAKE_X Giovanni Gherdovich 2019-11-11 18:05 ` [PATCH 3/6] x86,sched: Add support for frequency invariance on XEON_PHI_KNL/KNM Giovanni Gherdovich 2019-11-11 18:05 ` [PATCH 4/6] x86,sched: Add support for frequency invariance on ATOM_GOLDMONT* Giovanni Gherdovich 2019-11-11 18:05 ` [PATCH 5/6] x86,sched: Add support for frequency invariance on ATOM Giovanni Gherdovich 2019-11-11 18:05 ` [PATCH 6/6] x86: intel_pstate: handle runtime turbo disablement/enablement in freq. invariance Giovanni Gherdovich 2019-11-12 21:28 ` kbuild test robot 2019-11-13 12:26 ` Giovanni Gherdovich
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 0/6] Add support for frequency invariance for (some) x86' \ /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
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).