mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Andreas Herrmann <herrmann.der.user@googlemail.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
	linux-pm@lists.linux-foundation.org, x86@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] tools: add power/x86/turbostat - v2
Date: Wed, 17 Nov 2010 01:44:52 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1011170126280.24426@x980> (raw)
In-Reply-To: <20101116102916.GA4305@alberich.amd.com>

On Tue, 16 Nov 2010, Andreas Herrmann wrote:

> On Mon, Nov 15, 2010 at 11:01:05AM -0500, Len Brown wrote:
> > From: Len Brown <len.brown@intel.com>
> > 
> > turbostat displays actual processor frequency on modern
> > Intel processors.  Note that this capability depends on free-running
> > APERF and MPERF MSRs, which were cleared by the acpi_cpufreq
> > driver up through Linux-2.6.29.
> 
> Why isn't cpufreq-aperf sufficient for showing the actual frequency?
> The tool can handle both AMD and Intel CPUs.

Looking over its source code, I don't see any reason that cpufreq-aperf
wouldn't be sufficient for showing actual frequency, were that your goal.
I hadn't heard of this tool until your note.  I complied it, but I guess
I'm too lazy to figure out why it didnt' run.
It seems somewhat elaborate as compared to the task at hand...

> There is a CPUID flag which can be checked for APERF/MPERF existence,
> no need to enforce a general vendor check like this:
> 
>   $ ./turbostat
>   CPUID: AuthenticAMD != GenuineIntel

turbostat isn't very interesting on systems that don't
have a reliable TSC or C-state residency MSRs.  AFAIK,
AMD has neither.  If you have information to the contrary
and can test it on AMD hardware, I'd be happy to enable AMD,
as I have neither.

> > On Intel Core i3/i5/i7 (Nehalem) and newer processors,
> > turbostat displays residency in idle power saving states.
> 
> Can't this be added to cpuidle-info (see branch cpupowerutils in
> git://git.kernel.org/pub/scm/utils/kernel/cpufreq/cpufrequtils.git)?

I suppose it could if somebody were in need of a hobby.
However, if you want a big tool in this space,
you'd probably be better off running powertop2,
which will incorporate what turbostat does, and more.

> BTW, gcc v4.4 throws several warnings when compiling your
> code:

thanks, I'll fix these.

cheers,
Len Brown, Intel Open Source Technology Center

  reply	other threads:[~2010-11-17  6:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-23  5:31 [PATCH] tools: add power/x86/turbostat Len Brown
2010-10-24  4:06 ` [PATCH] tools: add power/x86/turbostat - v2 Len Brown
2010-10-27  3:14   ` [PATCH RESEND] " Len Brown
2010-11-15 16:01     ` Len Brown
2010-11-15 17:16       ` Otavio Salvador
2010-11-16 10:29       ` Andreas Herrmann
2010-11-17  6:44         ` Len Brown [this message]
2010-11-24  4:58       ` [PATCH v3] tools: create power/x86/turbostat Len Brown
2010-12-07  6:00         ` [PATCH v4] " Len Brown
2010-12-07 14:29           ` Thiago Farina
2011-02-11  4:43             ` 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=alpine.LFD.2.00.1011170126280.24426@x980 \
    --to=lenb@kernel.org \
    --cc=gregkh@suse.de \
    --cc=herrmann.der.user@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=x86@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

all inboxes | Powered by JetHome®