From: "Doug Smythies" <dsmythies@telus.net>
To: "'Qais Yousef'" <qais.yousef@arm.com>
Cc: "'Giovanni Gherdovich'" <ggherdovich@suse.cz>, <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>,
"'Peter Zijlstra'" <peterz@infradead.org>,
"'Vincent Guittot'" <vincent.guittot@linaro.org>,
"'Quentin Perret'" <qperret@qperret.net>,
"'Dietmar Eggemann'" <dietmar.eggemann@arm.com>,
"'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>
Subject: RE: [PATCH v4 1/6] x86,sched: Add support for frequency invariance
Date: Mon, 23 Dec 2019 08:34:04 -0800 [thread overview]
Message-ID: <000301d5b9ae$cd8f5b30$68ae1190$@net> (raw)
In-Reply-To: <20191223144043.ticfxfgbolsqk74i@e107158-lin.cambridge.arm.com>
On 2019.12.23 06:41 Qais Yousef wrote:
> On 12/23/19 14:07, Qais Yousef wrote:
>>> Re-boot to the nocgv1 (stock + cgroup_no_v1=all) kernel.
>>> set the schedutil governor.
>>> launch test 2 and related monitoring tools.
>>> verify performance governor like behavior.
>>
>> So as stated above, by default uclamp_{min, max} = (0, 1024). So it wouldn't
>> act as performance governor by default unless you explicitly write 1024 to
>> uclamp.min.
>>
>> Let me go find Ubuntu mainline tree to see if they applied anything extra in
>> there. If they modified the default behavior that could explain what you see.
>
> Actually I see what you were saying now that you copy the config. So I think
> I misunderstood and you are running Linus' 5.5-rc2 + Ubuntu PPA config.
Yes, exactly.
I have a clone of the main Linus git branch, but steal the kernel
configuration from the Ubuntu mainline PPA.
>
> I'm trying to to reproduce the issue at my end.
... Doug
next prev parent reply other threads:[~2019-12-23 16:34 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 [this message]
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
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='000301d5b9ae$cd8f5b30$68ae1190$@net' \
--to=dsmythies@telus.net \
--cc=bp@suse.de \
--cc=dietmar.eggemann@arm.com \
--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=peterz@infradead.org \
--cc=pjt@google.com \
--cc=qais.yousef@arm.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).