From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Doug Smythies <dsmythies@telus.net>
Cc: linux-pm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Len Brown <lenb@kernel.org>
Subject: Re: intel_pstate: Lowest frequency not reached with Intel i7-6700
Date: Thu, 13 Dec 2018 10:54:05 +0100 [thread overview]
Message-ID: <a4321c48-e9df-1a2a-cfbd-bac07a9c65d8@molgen.mpg.de> (raw)
In-Reply-To: <000701d4926f$533eb270$f9bc1750$@net>
[-- Attachment #1: Type: text/plain, Size: 2209 bytes --]
Dear Doug,
Thank you for your reply.
On 12/13/18 00:06, Doug Smythies wrote:
> On 2018.12.12 13:40 Paul Menzel wrote:
>
>> Using *powersave* as P-state selection algorithm, on an idle system
>
> Define "idle system".
> If your computer is running a GUI, or is even a server without a GUI
> but with many services running, then "idle" really isn't.
> Below is from my test server, with many services disabled, so
> "idle" really is quite "idle"
>
> doug@s15:~/temp$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,PkgTmp,PkgWatt --interval 15
> Busy% Bzy_MHz PkgTmp PkgWatt
> 0.01 1608 27 3.71
> 0.01 1619 27 3.71
> 0.01 1600 28 3.71
> 0.01 1600 28 3.70
>
> Note that p state 16 (1600 MHz) is the minimum for my older i7-2600k
> processor.
The thing is, on an Intel Kaby Lake laptop with Ubuntu 18.10 and GNOME
running, it goes down to the lowest listed frequency.
>> Shouldn’t it go down until 800 MHz?
>
> We would need some actual busy information, turbostat is the
> recommended tool, to know for sure.
Here you go.
```
tools/power/x86/turbostat> sudo ./turbostat --Summary --quiet --show Busy%,Bzy_MHz,PkgTmp,PkgWatt --interval 15
Busy% Bzy_MHz PkgTmp PkgWatt
3.59 1167 31 1.68
3.21 903 31 1.34
3.21 906 31 1.34
3.27 901 31 1.35
8.23 2715 30 2.32 ← stopping GDM (systemctl stop gdm)
2.95 915 30 1.18
2.91 906 30 1.18
2.92 903 30 1.17
2.90 900 29 1.17
2.89 903 29 1.18
2.91 903 30 1.18
2.89 903 29 1.18
2.89 900 29 1.18
2.90 903 30 1.18
2.90 903 29 1.17
2.90 903 29 1.17
2.90 900 29 1.16
2.90 903 29 1.14
2.90 903 28 1.11
2.90 903 29 1.10
2.91 900 29 1.16
2.91 903 29 1.14
2.90 903 29 1.12
2.90 903 29 1.16
2.90 900 28 1.17
2.92 903 29 1.16
2.90 903 29 1.16
2.90 903 29 1.16
```
800 MHz should be enough to keep GDM running, shouldn’t it?
Otherwise only SSH was running.
Kind regards,
Paul
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2018-12-13 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 23:06 intel_pstate: Lowest frequency not reached with Intel i7-6700 Doug Smythies
2018-12-13 9:54 ` Paul Menzel [this message]
2018-12-13 10:39 ` Rafael J. Wysocki
2018-12-13 12:41 ` Paul Menzel
2018-12-13 16:36 ` Srinivas Pandruvada
2018-12-13 16:21 ` Doug Smythies
-- strict thread matches above, loose matches on Subject: below --
2018-12-12 21:40 Paul Menzel
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=a4321c48-e9df-1a2a-cfbd-bac07a9c65d8@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=dsmythies@telus.net \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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).