All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Doug Smythies" <dsmythies@telus.net>
To: "'Rafael J. Wysocki'" <rafael@kernel.org>
Cc: "'Srinivas Pandruvada'" <srinivas.pandruvada@linux.intel.com>,
	"'Jörg Otte'" <jrg.otte@gmail.com>,
	"'Rafael J. Wysocki'" <rjw@rjwysocki.net>,
	"'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>,
	"'Linux PM list'" <linux-pm@vger.kernel.org>
Subject: RE: [intel-pstate driver regression] processor frequency very high even if in idle
Date: Fri, 1 Apr 2016 16:36:51 -0700	[thread overview]
Message-ID: <003901d18c6f$5ec91530$1c5b3f90$@net> (raw)
In-Reply-To: <CAJZ5v0gVvMg9FRGOkHCPJusCVG3JvEbF6kmnAtFziN+inOGiHA@mail.gmail.com>

On 2016.04.01 12:54 Rafael J. Wysocki wrote:
>On Fri, Apr 1, 2016 at 8:31 PM, Doug Smythies <dsmythies@telus.net> wrote:
>> On 2106.034.01 10:45 Srinivas Pandruvada wrote:
>>> On Fri, 2016-04-01 at 16:06 +0200, Jörg Otte wrote:
>> > > > > >
>>>> Done. Attached the tracer.
>>>> For me it looks like the previous one of the failing case.
>>>
>>> The traces show that idle task is constantly running without sleep.
>>
>> No, they (at least the first one, I didn't look at the next one yet)
>> show that CPUs 2 and 3 are spending around 99% of their time not in state
>> C0.

> How do you figure that out if I may ask?  It is not so obvious to me
> to be honest.

The trace was not in the form for the post processing tools, so I had
to manually import the trace into a spreadsheet and manually add new columns
calculated from the others.

Load = mperf / tsc * 100 % = C0 time.
Duration (mS) = tsc / 2.5e9 * 1000 
Note: I do not recall seeing an exact tsc for Jörg's computer, so I used
The 2.5 GHz from the device spec from some earlier e-mail.

Example (formatting will likely not send O.K.):

		CPU#	time		core_busy	scaled	from	to	mperf		aperf		tsc		freq		load		duration (ms)
<idle>-0	[002]	465.879451:	100		96		26	26	1826656	1826710	25062693	2500073	7.288%	10.025
<idle>-0	[003]	465.879484:	99		96		26	26	305796	305781	25147993	2499877	1.216%	10.059
<idle>-0	[000]	465.885794:	100		96		26	26	975908	975951	32434672	2500110	3.009%	12.974
<idle>-0	[001]	465.886898:	100		250		10	31	327356	327364	26673840	2500061	1.227%	10.670
<idle>-0	[002]	465.889527:	100		96		26	26	205336	205365	25133396	2500353	0.817%	10.053
<idle>-0	[003]	465.889555:	99		95		26	26	62544		62341		25117916	2491885	0.249%	10.047

> That the sample rate is ending up at ~10 Milliseconds, indicates some
> high frequency (>= 100Hz) events on those CPUs. Those events, apparently,
> take very little CPU time to complete, hence a load of about 1% on average.
>
> By the way, I can recreate the high sample rate with virtually no load
> on my system easy, but so far have been unable to get the high CPU
> frequencies observed by Jörg. I can get my system to about a target pstate of
> 20 where it should have remained at 16, but that is about it.
>
>> The driver is processing samples for idle task for every 10ms and
>> aperf/mperf are showing that we are always in turbo mode for idle task.
>
> That column pretty much always says "idle" (or swapper for my way of doing
> things). I have not found it to very useful as an indicator, and considerably
> more so since the utilization changes.
>
>>
>> Need to find out why idle task is not sleeping.
>
> I contend that is it.

Why?

Unless I misunderstood, because the trace data indicates that the those CPUs
are going into some deeper C stsate than C0 for most of their time.

... Doug



  reply	other threads:[~2016-04-01 23:36 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 17:24 [intel-pstate driver regression] processor frequency very high even if in idle Jörg Otte
2016-03-29 17:32 ` Jörg Otte
2016-03-29 21:34   ` Rafael J. Wysocki
2016-03-30 10:17     ` Jörg Otte
2016-03-30 11:05       ` Rafael J. Wysocki
2016-03-30 15:29         ` Jörg Otte
2016-03-30 18:39           ` Rafael J. Wysocki
2016-03-31  9:05             ` Jörg Otte
2016-03-31 11:42               ` Rafael J. Wysocki
2016-03-31 15:25                 ` Jörg Otte
2016-03-31 15:43                   ` Rafael J. Wysocki
2016-03-31 16:10                     ` Srinivas Pandruvada
2016-03-31 17:27                     ` Jörg Otte
2016-03-31 17:55                       ` Srinivas Pandruvada
2016-04-01  0:08                         ` Rafael J. Wysocki
2016-04-01  9:42                         ` Jörg Otte
2016-04-01 15:05                           ` Srinivas Pandruvada
2016-04-01 20:24                             ` Rafael J. Wysocki
2016-04-01  9:20                     ` Jörg Otte
2016-04-01 12:40                       ` Rafael J. Wysocki
2016-04-01 14:06                         ` Jörg Otte
2016-04-01 17:44                           ` Srinivas Pandruvada
2016-04-01 18:31                             ` Doug Smythies
2016-04-01 18:41                               ` Srinivas Pandruvada
2016-04-01 19:54                               ` Rafael J. Wysocki
2016-04-01 23:36                                 ` Doug Smythies [this message]
2016-04-02  0:28                                   ` Rafael J. Wysocki
2016-04-01 20:28                           ` Rafael J. Wysocki
2016-04-02 22:50                             ` Rafael J. Wysocki
2016-04-01 15:20                         ` Doug Smythies
2016-04-01 16:46                           ` Jörg Otte
2016-04-01 17:34                             ` Jörg Otte
2016-03-30 15:33         ` Pandruvada, Srinivas
2016-03-30 15:51           ` Jörg Otte
2016-03-30 18:50             ` Doug Smythies
2016-03-30 18:50               ` Doug Smythies
2016-03-30 18:58               ` Srinivas Pandruvada
2016-03-30 20:12                 ` Rafael J. Wysocki
2016-03-30 20:26                   ` Srinivas Pandruvada
2016-03-31  9:23                     ` Jörg Otte
2016-03-31 14:39                       ` Doug Smythies
2016-03-31 14:39                         ` Doug Smythies
2016-03-31 15:06                         ` Srinivas Pandruvada
2016-03-31 15:32                           ` Jörg Otte
2016-03-31 15:10                         ` Doug Smythies
2016-03-31 15:10                           ` Doug Smythies
2016-04-01  7:20                       ` Doug Smythies
2016-04-01  7:20                         ` Doug Smythies
  -- strict thread matches above, loose matches on Subject: below --
2016-03-30 21:41 Sedat Dilek
2016-03-30 21:58 ` Rafael J. Wysocki
2016-03-30 22:23   ` Sedat Dilek
2016-03-30 22:29     ` Rafael J. Wysocki
2016-03-30 22:18 ` Srinivas Pandruvada
2016-03-30 22:25   ` Rafael J. Wysocki
2016-03-30 22:46     ` Srinivas Pandruvada
2016-03-30 23:17       ` Pandruvada, Srinivas
2016-03-30 23:25         ` Sedat Dilek
2016-03-30 23:28           ` Rafael J. Wysocki
2016-03-30 23:32             ` Sedat Dilek
2016-03-30 23:41               ` Rafael J. Wysocki
2016-03-31  6:38                 ` Sedat Dilek
2016-03-31  7:45                   ` Sedat Dilek
     [not found]                 ` <CAA=4085Mmv7gRpJid8UGQ4ti6c1HhaENnogd8aPrg6E-w68QWg@mail.gmail.com>
2016-03-31  7:28                   ` Navin P.S
2016-03-30 22:50   ` Doug Smythies
2016-03-30 23:12     ` Srinivas Pandruvada
2016-03-31  8:10     ` Sedat Dilek
2016-03-31 14:30       ` Doug Smythies
2016-03-31 14:30         ` Doug Smythies
2016-04-02  6:12         ` Sedat Dilek
     [not found]           ` <CA+icZUVHyq7dOh457rYv+2nmNxPevY0ZcqxhQVhYG4Z1D-NaDA@mail.gmail.com>
2016-04-02 15:28             ` Srinivas Pandruvada
2016-04-02 17:19               ` Jörg Otte
2016-04-02 18:20                 ` Sedat Dilek
2016-04-03 18:59                   ` Doug Smythies
2016-04-03 18:59                     ` Doug Smythies
2016-04-04  5:13                     ` Sedat Dilek
2016-04-04  6:14                       ` Doug Smythies
2016-04-04  6:14                         ` Doug Smythies
2016-04-04 14:12                         ` Sedat Dilek

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='003901d18c6f$5ec91530$1c5b3f90$@net' \
    --to=dsmythies@telus.net \
    --cc=jrg.otte@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.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 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.