linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Doug Smythies" <dsmythies@telus.net>
To: 'Len Brown' <lenb@kernel.org>
Cc: 'Len Brown' <len.brown@intel.com>, linux-pm@vger.kernel.org
Subject: RE: [PATCH 01/12] tools/power turbostat: simplify default output
Date: Sun, 19 Apr 2015 07:26:24 -0700	[thread overview]
Message-ID: <000301d07aac$d1856bd0$74904370$@net> (raw)
In-Reply-To: <1cc21f7b6b747220c29b42cfd1c84b5648d12407.1429402554.git.len.brown@intel.com>

On 2015.04.18 17:40 Len Brown wrote:

> Casual turbostat users generally just want to know MHz.
> So by default, just print enough information to make sense of MHz.
> 
> All the other configuration data and columns for C-states and temperature etc,
> are printed with the --debug option.

I almost never use turbostat to obtain MHz.
I only use turbostat to observe Energy or Power, and C-states.

I am not in favor of this change.

I do not want the extra clutter that comes with the --debug option
(although I do use it sometimes).
When doing experiments manually, without a script, it is convenient
to have many energy or power samples visible on the screen all at once.

Note: If I am using the acpi cpufreq driver (i.e. rarely), then yes
I use turbostat to obtain actual CPU frequencies, as I know of no
other way.

I reviewed some help type forums, and yes while many postings involving
turbostat are about CPU frequency, there are also some about power.



  parent reply	other threads:[~2015-04-19 14:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-19  0:40 turbostat patches for Linux-4.1 Len Brown
2015-04-19  0:40 ` [PATCH 01/12] tools/power turbostat: simplify default output Len Brown
2015-04-19  0:40   ` [PATCH 02/12] tools/power turbostat: update PERF_LIMIT_REASONS decoding Len Brown
2015-04-19  0:40   ` [PATCH 03/12] tools/power turbostat: label base frequency Len Brown
2015-04-19  0:40   ` [PATCH 04/12] x86 msr-index: define MSR_TURBO_RATIO_LIMIT,1,2 Len Brown
2015-04-19  0:40   ` [PATCH 05/12] tools/power turbostat: use new MSR_TURBO_RATIO_LIMIT names Len Brown
2015-04-19  0:40   ` [PATCH 06/12] tools/power turbostat: dump MSR_TURBO_RATIO_LIMIT2 Len Brown
2015-04-19  0:40   ` [PATCH 07/12] tools/power turbostat: modprobe msr, if needed Len Brown
2015-04-19 14:29     ` Doug Smythies
2015-04-19  0:40   ` [PATCH 08/12] tools/power turbostat: Use $(CURDIR) instead of $(PWD) and add support for O= option in Makefile Len Brown
2015-04-19  0:40   ` [PATCH 09/12] tools/power turbostat: Initial Skylake support Len Brown
2015-04-19  0:40   ` [PATCH 10/12] tools/power turbostat: correct DRAM RAPL units on recent Xeon processors Len Brown
2015-04-19  0:40   ` [PATCH 11/12] tools/power turbostat: calculate TSC frequency from CPUID(0x15) on SKL Len Brown
2015-04-19  0:40   ` [PATCH 12/12] tools/power turbostat: correct dumped pkg-cstate-limit value Len Brown
2015-04-19 14:26   ` Doug Smythies [this message]
2015-04-19 21:02     ` [PATCH 01/12] tools/power turbostat: simplify default output Len Brown

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='000301d07aac$d1856bd0$74904370$@net' \
    --to=dsmythies@telus.net \
    --cc=len.brown@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-pm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).