From: Peter Zijlstra <peterz@infradead.org>
To: Giovanni Gherdovich <ggherdovich@suse.cz>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@suse.de>,
Len Brown <lenb@kernel.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
x86@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Mel Gorman <mgorman@techsingularity.net>,
Matt Fleming <matt@codeblueprint.co.uk>,
Viresh Kumar <viresh.kumar@linaro.org>,
Juri Lelli <juri.lelli@redhat.com>, Paul Turner <pjt@google.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Quentin Perret <qperret@qperret.net>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Doug Smythies <dsmythies@telus.net>
Subject: Re: [PATCH v4 3/6] x86,sched: Add support for frequency invariance on XEON_PHI_KNL/KNM
Date: Wed, 18 Dec 2019 21:22:36 +0100 [thread overview]
Message-ID: <20191218202236.GJ11457@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20191113124654.18122-4-ggherdovich@suse.cz>
On Wed, Nov 13, 2019 at 01:46:51PM +0100, Giovanni Gherdovich wrote:
> The scheduler needs the ratio freq_curr/freq_max for frequency-invariant
> accounting. On Xeon Phi CPUs set freq_max to the second-highest frequency
> reported by the CPU.
>
> Xeon Phi CPUs such as Knights Landing and Knights Mill typically have either
> one or two turbo frequencies; in the former case that's 100 MHz above the base
> frequency, in the latter case the two levels are 100 MHz and 200 MHz above
> base frequency.
>
> We set freq_max to the second-highest frequency reported by the CPU. This
> could be the base frequency (if only one turbo level is available) or the first
> turbo level (if two levels are available). The rationale is to compromise
> between power efficiency or performance -- going straight to max turbo would
> favor efficiency and blindly using base freq would favor performance.
>
> For reference, this is how MSR_TURBO_RATIO_LIMIT must be parsed on a Xeon Phi
> to get the available frequencies (taken from a comment in turbostat's sources):
>
> [0] -- Reserved
> [7:1] -- Base value of number of active cores of bucket 1.
> [15:8] -- Base value of freq ratio of bucket 1.
> [20:16] -- +ve delta of number of active cores of bucket 2.
> i.e. active cores of bucket 2 =
> active cores of bucket 1 + delta
> [23:21] -- Negative delta of freq ratio of bucket 2.
> i.e. freq ratio of bucket 2 =
> freq ratio of bucket 1 - delta
> [28:24]-- +ve delta of number of active cores of bucket 3.
> [31:29]-- -ve delta of freq ratio of bucket 3.
> [36:32]-- +ve delta of number of active cores of bucket 4.
> [39:37]-- -ve delta of freq ratio of bucket 4.
> [44:40]-- +ve delta of number of active cores of bucket 5.
> [47:45]-- -ve delta of freq ratio of bucket 5.
> [52:48]-- +ve delta of number of active cores of bucket 6.
> [55:53]-- -ve delta of freq ratio of bucket 6.
> [60:56]-- +ve delta of number of active cores of bucket 7.
> [63:61]-- -ve delta of freq ratio of bucket 7.
Does it make sense to write a complete decoder and pass a @size
parameter just like the skx/glm case?
(I've no idea on the 4 I passed in, probably wants to be something else)
---
Index: linux-2.6/arch/x86/kernel/smpboot.c
===================================================================
--- linux-2.6.orig/arch/x86/kernel/smpboot.c
+++ linux-2.6/arch/x86/kernel/smpboot.c
@@ -1863,36 +1863,12 @@ static const struct x86_cpu_id has_glm_t
{}
};
-static int get_knl_turbo_ratio(u64 *turbo_ratio)
+static bool knl_set_cpu_max_freq(u64 *ratio, u64 *turbo_ratio, int size)
{
+ int delta_cores, delta_fratio;
+ int cores, fratio;
+ int err, i;
u64 msr;
- u32 ratio, delta_ratio;
- int err, i, found = 0;
-
- err = rdmsrl_safe(MSR_TURBO_RATIO_LIMIT, &msr);
- if (err)
- return err;
-
- ratio = (msr >> 8) & 0xFF;
-
- for (i = 16; i < 64; i += 8) {
- delta_ratio = (msr >> (i + 5)) & 0x7;
- if (delta_ratio) {
- *turbo_ratio = ratio - delta_ratio;
- found = 1;
- break;
- }
- }
-
- if (!found)
- return 1;
-
- return 0;
-}
-
-static bool knl_set_cpu_max_freq(u64 *ratio, u64 *turbo_ratio)
-{
- int err;
if (!x86_match_cpu(has_knl_turbo_ratio_limits))
return false;
@@ -1901,15 +1877,32 @@ static bool knl_set_cpu_max_freq(u64 *ra
if (err)
return false;
- /* second highest turbo ratio */
- err = get_knl_turbo_ratio(turbo_ratio);
+ *ratio = (*ratio >> 8) & 0xFF; /* max P state ratio */
+
+ err = rdmsrl_safe(MSR_TURBO_RATIO_LIMIT, &msr);
if (err)
return false;
- /* max P state ratio */
- *ratio = (*ratio >> 8) & 0xFF;
+ cores = (msr >> 1) & 0x7F;
+ fratio = (msr >> 8) & 0xFF;
- return true;
+ i = 16;
+ do {
+ if (cores >= size) {
+ *turbo_ratio = fratio;
+ return true;
+ }
+
+ delta_cores = (msr >> i) & 0x1F;
+ delta_fratio = (msr >> (i + 5)) & 0x07;
+
+ cores += delta_cores;
+ fratio -= delta_fratio;
+
+ i += 8;
+ } while (i < 64);
+
+ return false;
}
static bool skx_set_cpu_max_freq(u64 *ratio, u64 *turbo_ratio, int size)
@@ -1975,7 +1968,7 @@ static void intel_set_cpu_max_freq(void)
skx_set_cpu_max_freq(&ratio, &turbo_ratio, 1))
goto set_value;
- if (knl_set_cpu_max_freq(&ratio, &turbo_ratio))
+ if (knl_set_cpu_max_freq(&ratio, &turbo_ratio, 4))
goto set_value;
if (x86_match_cpu(has_skx_turbo_ratio_limits) &&
next prev parent reply other threads:[~2019-12-18 20:22 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 12:46 [PATCH v4 0/6] Add support for frequency invariance for (some) x86 Giovanni Gherdovich
2019-11-13 12:46 ` [PATCH v4 1/6] x86,sched: Add support for frequency invariance Giovanni Gherdovich
2019-11-24 7:49 ` Doug Smythies
2019-11-25 8:16 ` Doug Smythies
2019-11-25 9:16 ` Mel Gorman
2019-11-25 16:06 ` Giovanni Gherdovich
2019-11-26 5:59 ` Doug Smythies
2019-11-26 15:20 ` Giovanni Gherdovich
2019-11-27 7:32 ` Doug Smythies
2019-11-28 22:48 ` Doug Smythies
2019-12-19 10:48 ` Qais Yousef
2019-12-23 7:47 ` Doug Smythies
2019-12-23 14:07 ` Qais Yousef
2019-12-23 14:40 ` Qais Yousef
2019-12-23 16:34 ` Doug Smythies
2019-12-23 19:10 ` Qais Yousef
2019-12-24 1:16 ` Doug Smythies
2019-12-24 11:08 ` Qais Yousef
2019-12-02 16:34 ` Ionela Voinescu
2019-12-06 11:57 ` Giovanni Gherdovich
2019-12-18 19:34 ` Peter Zijlstra
2019-12-19 20:27 ` Giovanni Gherdovich
2019-11-13 12:46 ` [PATCH v4 2/6] x86,sched: Add support for frequency invariance on SKYLAKE_X Giovanni Gherdovich
2019-12-18 20:06 ` Peter Zijlstra
2019-12-19 20:29 ` Giovanni Gherdovich
2019-11-13 12:46 ` [PATCH v4 3/6] x86,sched: Add support for frequency invariance on XEON_PHI_KNL/KNM Giovanni Gherdovich
2019-12-18 20:22 ` Peter Zijlstra [this message]
2019-12-19 20:32 ` Giovanni Gherdovich
2019-11-13 12:46 ` [PATCH v4 4/6] x86,sched: Add support for frequency invariance on ATOM_GOLDMONT* Giovanni Gherdovich
2019-11-13 12:46 ` [PATCH v4 5/6] x86,sched: Add support for frequency invariance on ATOM Giovanni Gherdovich
2019-11-13 16:50 ` Srinivas Pandruvada
2019-11-15 10:34 ` Giovanni Gherdovich
2019-11-13 12:46 ` [PATCH v4 6/6] x86: intel_pstate: handle runtime turbo disablement/enablement in freq. invariance Giovanni Gherdovich
2019-12-18 20:37 ` [PATCH v4 0/6] Add support for frequency invariance for (some) x86 Peter Zijlstra
2019-12-19 20:33 ` 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 \
--in-reply-to=20191218202236.GJ11457@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@suse.de \
--cc=dietmar.eggemann@arm.com \
--cc=dsmythies@telus.net \
--cc=ggherdovich@suse.cz \
--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=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).