From: Julia Lawall <julia.lawall@inria.fr>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Francisco Jerez <currojerez@riseup.net>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Len Brown <lenb@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: cpufreq: intel_pstate: map utilization into the pstate range
Date: Mon, 3 Jan 2022 17:41:51 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2201031741290.3020@hadrien> (raw)
In-Reply-To: <CAJZ5v0im+Cke7tcNRav2VCyf5Qvi7qC29aF+9A1kVZZmt7cu6g@mail.gmail.com>
> > > Can you please run the 32 spinning threads workload (ie. on one
> > > package) and with P-state locked to 10 and then to 20 under turbostat
> > > and send me the turbostat output for both runs?
> >
> > Attached.
> >
> > Pstate 10: spin_minmax_10_dahu-9_5.15.0freq_schedutil_11.turbo
> > Pstate 20: spin_minmax_20_dahu-9_5.15.0freq_schedutil_11.turbo
>
> Well, in both cases there is only 1 CPU running and it is running at
> 1 GHz (ie. P-state 10) all the time as far as I can say.
Indeed. I'll check on that.
julia
next prev parent reply other threads:[~2022-01-03 16:42 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 22:52 cpufreq: intel_pstate: map utilization into the pstate range Julia Lawall
2021-12-17 18:36 ` Rafael J. Wysocki
2021-12-17 19:32 ` Julia Lawall
2021-12-17 20:36 ` Francisco Jerez
2021-12-17 22:51 ` Julia Lawall
2021-12-18 0:04 ` Francisco Jerez
2021-12-18 6:12 ` Julia Lawall
2021-12-18 10:19 ` Francisco Jerez
2021-12-18 11:07 ` Julia Lawall
2021-12-18 22:12 ` Francisco Jerez
2021-12-19 6:42 ` Julia Lawall
2021-12-19 14:19 ` Rafael J. Wysocki
2021-12-19 14:30 ` Rafael J. Wysocki
2021-12-19 21:47 ` Julia Lawall
2021-12-19 22:10 ` Francisco Jerez
2021-12-19 22:41 ` Julia Lawall
2021-12-19 23:31 ` Francisco Jerez
2021-12-21 17:04 ` Rafael J. Wysocki
2021-12-21 23:56 ` Francisco Jerez
2021-12-22 14:54 ` Rafael J. Wysocki
2021-12-24 11:08 ` Julia Lawall
2021-12-28 16:58 ` Julia Lawall
2021-12-28 17:40 ` Rafael J. Wysocki
2021-12-28 17:46 ` Julia Lawall
2021-12-28 18:06 ` Rafael J. Wysocki
2021-12-28 18:16 ` Julia Lawall
2021-12-29 9:13 ` Julia Lawall
2021-12-30 17:03 ` Rafael J. Wysocki
2021-12-30 17:54 ` Julia Lawall
2021-12-30 17:58 ` Rafael J. Wysocki
2021-12-30 18:20 ` Julia Lawall
2021-12-30 18:37 ` Rafael J. Wysocki
2021-12-30 18:44 ` Julia Lawall
2022-01-03 15:50 ` Rafael J. Wysocki
2022-01-03 16:41 ` Julia Lawall [this message]
2022-01-03 18:23 ` Julia Lawall
2022-01-03 19:58 ` Rafael J. Wysocki
2022-01-03 20:51 ` Julia Lawall
2022-01-04 14:09 ` Rafael J. Wysocki
2022-01-04 15:49 ` Julia Lawall
2022-01-04 19:22 ` Rafael J. Wysocki
2022-01-05 20:19 ` Julia Lawall
2022-01-05 23:46 ` Francisco Jerez
2022-01-06 19:49 ` Julia Lawall
2022-01-06 20:28 ` Srinivas Pandruvada
2022-01-06 20:43 ` Julia Lawall
2022-01-06 21:55 ` srinivas pandruvada
2022-01-06 21:58 ` Julia Lawall
2022-01-05 0:38 ` Francisco Jerez
2021-12-19 14:14 ` Rafael J. Wysocki
2021-12-19 17:03 ` Julia Lawall
2021-12-19 22:30 ` Francisco Jerez
2021-12-21 18:10 ` Rafael J. Wysocki
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=alpine.DEB.2.22.394.2201031741290.3020@hadrien \
--to=julia.lawall@inria.fr \
--cc=currojerez@riseup.net \
--cc=juri.lelli@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.