From: Mascha Kurpicz <mascha.kurpicz@unine.ch>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
Maxime Colmant <maxime.colmant@inria.fr>
Subject: Re: time_in_state on Ubuntu 13.10
Date: Tue, 29 Apr 2014 10:38:32 +0200 [thread overview]
Message-ID: <535F6508.5020202@unine.ch> (raw)
In-Reply-To: <CAKohponpGMMRUvDivaxj_qz5dQvhxZHiHW4Z19GzpaEJHGStRQ@mail.gmail.com>
On 04/29/2014 10:26 AM, Viresh Kumar wrote:
> On 29 April 2014 12:47, Mascha Kurpicz <mascha.kurpicz@unine.ch> wrote:
>> Sorry for the imprecision.
>>
>> Works correctly with
>> Ubuntu 12.04.3 LTS - kernel 3.2.0-29-generic
>> Ubuntu 12.04.3 LTS - kernel 3.8.0-29
>> Ubuntu 13.10 - kernel 3.8.0-29-generic
>>
>> 0 or very small (e.g. 6) values with
>> Ubuntu 13.10 - kernel 3.11.0-20-generic
> Can you provide cpufreq-info 's output for the last two cases please?
>
> i.e.
>> Ubuntu 13.10 - kernel 3.8.0-29-generic
user@ubuntu1310:~$ cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 1.60 GHz - 3.10 GHz
available frequency steps: 3.10 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz,
2.20 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz
available cpufreq governors: conservative, ondemand, userspace,
powersave, performance
current policy: frequency should be within 1.60 GHz and 3.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
cpufreq stats: 3.10 GHz:26.39%, 2.80 GHz:0.13%, 2.60 GHz:0.23%, 2.40
GHz:0.20%, 2.20 GHz:0.20%, 2.00 GHz:0.30%, 1.80 GHz:0.26%, 1.60
GHz:72.28% (1742)
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 10.0 us.
hardware limits: 1.60 GHz - 3.10 GHz
available frequency steps: 3.10 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz,
2.20 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz
available cpufreq governors: conservative, ondemand, userspace,
powersave, performance
current policy: frequency should be within 1.60 GHz and 3.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
cpufreq stats: 3.10 GHz:2.17%, 2.80 GHz:0.04%, 2.60 GHz:0.07%, 2.40
GHz:0.09%, 2.20 GHz:1.06%, 2.00 GHz:0.31%, 1.80 GHz:0.42%, 1.60
GHz:95.84% (2752)
analyzing CPU 2:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3
CPUs which need to have their frequency coordinated by software: 2
maximum transition latency: 10.0 us.
hardware limits: 1.60 GHz - 3.10 GHz
available frequency steps: 3.10 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz,
2.20 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz
available cpufreq governors: conservative, ondemand, userspace,
powersave, performance
current policy: frequency should be within 1.60 GHz and 3.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
cpufreq stats: 3.10 GHz:2.24%, 2.80 GHz:0.00%, 2.60 GHz:0.02%, 2.40
GHz:0.01%, 2.20 GHz:0.01%, 2.00 GHz:0.09%, 1.80 GHz:0.00%, 1.60
GHz:97.63% (431)
analyzing CPU 3:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3
CPUs which need to have their frequency coordinated by software: 3
maximum transition latency: 10.0 us.
hardware limits: 1.60 GHz - 3.10 GHz
available frequency steps: 3.10 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz,
2.20 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz
available cpufreq governors: conservative, ondemand, userspace,
powersave, performance
current policy: frequency should be within 1.60 GHz and 3.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
cpufreq stats: 3.10 GHz:1.49%, 2.80 GHz:0.00%, 2.60 GHz:0.03%, 2.40
GHz:0.03%, 2.20 GHz:0.01%, 2.00 GHz:0.01%, 1.80 GHz:0.01%, 1.60
GHz:98.43% (560)
>> Ubuntu 13.10 - kernel 3.11.0-20-generic
user@ubuntu1310:~$ cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 1.60 GHz - 3.10 GHz
available frequency steps: 3.10 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz,
2.20 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz
available cpufreq governors: conservative, ondemand, userspace,
powersave, performance
current policy: frequency should be within 1.60 GHz and 3.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
cpufreq stats: 3.10 GHz:-nan%, 2.80 GHz:-nan%, 2.60 GHz:-nan%, 2.40
GHz:-nan%, 2.20 GHz:-nan%, 2.00 GHz:-nan%, 1.80 GHz:-nan%, 1.60
GHz:-nan% (75)
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 10.0 us.
hardware limits: 1.60 GHz - 3.10 GHz
available frequency steps: 3.10 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz,
2.20 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz
available cpufreq governors: conservative, ondemand, userspace,
powersave, performance
current policy: frequency should be within 1.60 GHz and 3.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
cpufreq stats: 3.10 GHz:-nan%, 2.80 GHz:-nan%, 2.60 GHz:-nan%, 2.40
GHz:-nan%, 2.20 GHz:-nan%, 2.00 GHz:-nan%, 1.80 GHz:-nan%, 1.60
GHz:-nan% (71)
analyzing CPU 2:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 2
CPUs which need to have their frequency coordinated by software: 2
maximum transition latency: 10.0 us.
hardware limits: 1.60 GHz - 3.10 GHz
available frequency steps: 3.10 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz,
2.20 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz
available cpufreq governors: conservative, ondemand, userspace,
powersave, performance
current policy: frequency should be within 1.60 GHz and 3.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
cpufreq stats: 3.10 GHz:-nan%, 2.80 GHz:-nan%, 2.60 GHz:-nan%, 2.40
GHz:-nan%, 2.20 GHz:-nan%, 2.00 GHz:-nan%, 1.80 GHz:-nan%, 1.60
GHz:-nan% (16)
analyzing CPU 3:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 3
CPUs which need to have their frequency coordinated by software: 3
maximum transition latency: 10.0 us.
hardware limits: 1.60 GHz - 3.10 GHz
available frequency steps: 3.10 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz,
2.20 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz
available cpufreq governors: conservative, ondemand, userspace,
powersave, performance
current policy: frequency should be within 1.60 GHz and 3.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
cpufreq stats: 3.10 GHz:-nan%, 2.80 GHz:-nan%, 2.60 GHz:-nan%, 2.40
GHz:-nan%, 2.20 GHz:-nan%, 2.00 GHz:-nan%, 1.80 GHz:-nan%, 1.60
GHz:-nan% (6)
next prev parent reply other threads:[~2014-04-29 8:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 14:43 time_in_state on Ubuntu 13.10 Mascha Kurpicz
2014-04-29 4:28 ` Viresh Kumar
2014-04-29 7:17 ` Mascha Kurpicz
2014-04-29 8:26 ` Viresh Kumar
2014-04-29 8:38 ` Mascha Kurpicz [this message]
2014-05-02 5:25 ` Viresh Kumar
2014-05-05 12:08 ` Mascha Kurpicz
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=535F6508.5020202@unine.ch \
--to=mascha.kurpicz@unine.ch \
--cc=cpufreq@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=maxime.colmant@inria.fr \
--cc=rjw@rjwysocki.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox