From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: Francisco Jerez <currojerez@riseup.net>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Giovanni Gherdovich <ggherdovich@suse.cz>,
Doug Smythies <dsmythies@telus.net>
Subject: Re: [PATCH] cpufreq: intel_pstate: Implement passive mode with HWP enabled
Date: Thu, 16 Jul 2020 16:33:34 +0200 [thread overview]
Message-ID: <CAJZ5v0hm-evY87JkG=Aru2Z_gFwcjB7XD+pJgM4iMSQJkrmtrw@mail.gmail.com> (raw)
In-Reply-To: <44797cd1312843e5998070aec236b1cd80c48d14.camel@linux.intel.com>
On Thu, Jul 16, 2020 at 3:14 AM Srinivas Pandruvada
<srinivas.pandruvada@linux.intel.com> wrote:
>
> On Wed, 2020-07-15 at 14:35 -0700, Francisco Jerez wrote:
> > "Rafael J. Wysocki" <rafael@kernel.org> writes:
> >
> > > On Wed, Jul 15, 2020 at 2:09 AM Francisco Jerez <
> > > currojerez@riseup.net> wrote:
> > > > "Rafael J. Wysocki" <rjw@rjwysocki.net> writes:
> > > >
> > > > > From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > > > >
>
> [...]
>
> > > > > I don't think that's accurate. I've looked at hundreds of
> > > > > traces
> > while
> > my series [1] was in control of HWP_REQ_MAX and I've never seen an
> > excursion above the maximum HWP_REQ_MAX control specified by it
> > within a
> > given P-state domain, even while that maximum specified was well into
> > the turbo range. So, yeah, I agree that HWP_REQ_MAX is nothing like
> > a
> > hard limit, particularly when multiple threads are running on the
> > same
> > clock domain, but the processor will still make its best effort to
> > limit
> > the clock frequency to the maximum of the requested maximums, even if
> > it
> > happens to be within the turbo range. That doesn't make it useless.
> > The exact same thing can be said about controlling HWP_REQ_MIN as
> > you're
> > doing now in this revision of your patch, BTW.
> >
> > If you don't believe me here is the turbostat sample with maximum
> > Bzy_MHz I get on the computer I'm sitting on right now while
> > compiling a
> > kernel on CPU0 if I set HWP_REQ_MAX to 0x1c (within the turbo range):
> >
> > > Core CPU Avg_MHz
> > > Busy% Bzy_MHz HWP_REQ PkgWatt CorWatt
> > > - - 757 27.03 2800 0x0000000000000000 7.1
> > > 3 4.90
> > > 0 0 2794 99.77 2800 0x0000000080001c04 7.1
> > > 3 4.90
> > > 0 2 83 2.98 2800 0x0000000080001c04
> > > 1 1 73 2.60 2800 0x0000000080001c04
> > > 1 3 78 2.79 2800 0x0000000080001c04
> >
> > With the default HWP_REQUEST:
> >
> > > Core CPU Avg_MHz
> > > Busy% Bzy_MHz HWP_REQ PkgWatt CorWatt
> > > - - 814 27.00 3015 0x0000000000000000 8.4
> > > 9 6.18
> > > 0 0 2968 98.24 3021 0x0000000080001f04 8.4
> > > 9 6.18
> > > 0 2 84 2.81 2982 0x0000000080001f04
> > > 1 1 99 3.34 2961 0x0000000080001f04
> > > 1 3 105 3.60 2921 0x0000000080001f04
>
> Correct. In HWP mode this is possible to lower limit in turbo region
> conditionally. In legacy mode you can't with turbo activation ratio.
>
> But what we don't want set max and min perf and use like desired to run
> at a P-state overriding HWP or limit the range where HWP can't do any
> meaningful selection.
That's a good point too IMO.
next prev parent reply other threads:[~2020-07-16 14:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 18:16 [PATCH] cpufreq: intel_pstate: Implement passive mode with HWP enabled Rafael J. Wysocki
2020-07-15 0:09 ` Francisco Jerez
2020-07-15 12:04 ` Rafael J. Wysocki
2020-07-15 21:35 ` Francisco Jerez
2020-07-16 1:14 ` Srinivas Pandruvada
2020-07-16 14:33 ` Rafael J. Wysocki [this message]
2020-07-16 14:32 ` Rafael J. Wysocki
2020-07-17 0:21 ` Francisco Jerez
2020-07-19 19:06 ` Rafael J. Wysocki
2020-07-20 23:20 ` Francisco Jerez
2020-07-21 16:25 ` Srinivas Pandruvada
2020-07-21 23:14 ` Francisco Jerez
2020-07-27 17:23 ` Rafael J. Wysocki
2020-07-27 17:15 ` Rafael J. Wysocki
2020-07-28 2:32 ` Francisco Jerez
2020-07-28 18:27 ` Rafael J. Wysocki
2020-07-29 5:46 ` Francisco Jerez
2020-07-29 17:52 ` Rafael J. Wysocki
2020-07-30 0:49 ` Francisco Jerez
2020-07-31 17:52 ` Rafael J. Wysocki
2020-07-31 22:43 ` Francisco Jerez
2020-07-28 15:41 ` Rafael J. Wysocki
2020-07-15 20:39 ` Doug Smythies
2020-07-16 12:07 ` Rafael J. Wysocki
2020-07-17 13:37 ` Doug Smythies
2020-07-19 11:42 ` Rafael J. Wysocki
2020-08-02 15:17 ` Doug Smythies
2020-08-03 17:08 ` Rafael J. Wysocki
2020-08-06 5:54 ` Doug Smythies
2020-08-06 11:39 ` 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='CAJZ5v0hm-evY87JkG=Aru2Z_gFwcjB7XD+pJgM4iMSQJkrmtrw@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=currojerez@riseup.net \
--cc=dsmythies@telus.net \
--cc=ggherdovich@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
/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).