linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Joonas Saarinen <jza@saunalahti.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD Bobcat cpufreq
Date: Fri, 18 Oct 2013 15:36:30 +0200	[thread overview]
Message-ID: <20131018133630.GD1007@pd.tnic> (raw)
In-Reply-To: <31997499.9414731382102390275.JavaMail.jza@saunalahti.fi>

On Fri, Oct 18, 2013 at 04:19:49PM +0300, Joonas Saarinen wrote:
> It's promising that the boost state support is "supported and
> active" but the output is still kind of sparse. There's no mention
> about specific turbo states,

could be bug in the tool...

> nor do I get /proc/cpuinfo or that cpupower tool ever to show an
> evidence that the CPU is going to 1333MHz. On Windows CPU-Z showed it
> constantly visiting that state.

You can also try turbostat in tools/power/x86/turbostat/

# ./turbostat -i 1

to give you core freq. readout every second and then pin a workload on
one core in another shell, say kernel build:

$ taskset 1 make

You should be able to see core 0 boosting like in my case:

cor CPU   GHz  TSC
        3.90 4.01
  0   0 4.17 4.01
  1   1 4.17 4.01
  2   2 2.23 4.01
  3   3 2.74 4.01
  4   4 1.83 4.01
  5   5 3.23 4.01
  6   6 1.69 4.01
  7   7 1.43 4.01

cores 0 and 1 go over 4GHz which is their boosted state.

HTH.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-10-18 13:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18 13:19 AMD Bobcat cpufreq Joonas Saarinen
2013-10-18 13:36 ` Borislav Petkov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-10-18 15:23 Joonas Saarinen
2013-10-18 15:36 ` Borislav Petkov
2013-10-17 20:54 Joonas Saarinen
2013-10-17 22:20 ` Borislav Petkov
2013-08-20 19:58 Joonas Saarinen
2013-08-22 11:17 ` Borislav Petkov

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=20131018133630.GD1007@pd.tnic \
    --to=bp@alien8.de \
    --cc=jza@saunalahti.fi \
    --cc=linux-kernel@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).