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 17:36:50 +0200 [thread overview]
Message-ID: <20131018153650.GE1007@pd.tnic> (raw)
In-Reply-To: <26801338.9419821382109781265.JavaMail.jza@saunalahti.fi>
On Fri, Oct 18, 2013 at 06:23:01PM +0300, Joonas Saarinen wrote:
> Borislav Petkov [bp@alien8.de] wrote:
> >You can also try turbostat in tools/power/x86/turbostat/
> >
> ># ./turbostat -i 1
>
> We might be on to something. With work pinned on one core:
>
> cor CPU GHz TSC
> 1.16 1.00
> 0 0 1.17 1.00
> 1 1 0.80 1.00
>
> When both cores are occupied:
>
> cor CPU GHz TSC
> 1.00 1.00
> 0 0 1.00 1.00
> 1 1 1.00 1.00
>
> In this case both cores are limited to 1GHz, but it might be intentional
> to avoid overheating.
That's the boosting algorithm - the more parts of the silicon consume
power, the more it gets spread out amongst them so that each one of them
gets a smaller amount of the remaining power up to the TDP which is
available for consumption.
Also, AFAICT, on those machines the boosting algorithm involves the GPU
so that it boosts too. This might be the reason why you don't see 1.33
GHz with one of the cores.
> So there is some turbo functionality indeed. The frequency shown by
> turbostat is still a bit off the target, not sure if there is any
> actual problem though.
Yeah, see above.
I think all is fine with your box :)
HTH.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-10-18 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 15:23 AMD Bobcat cpufreq Joonas Saarinen
2013-10-18 15:36 ` Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-18 13:19 Joonas Saarinen
2013-10-18 13: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=20131018153650.GE1007@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 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.