linux-kernel - Re: AMD Bobcat cpufreq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 18 Oct 2013 17:36:50 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Joonas Saarinen <jza@...nalahti.fi>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: AMD Bobcat cpufreq

On Fri, Oct 18, 2013 at 06:23:01PM +0300, Joonas Saarinen wrote:
> Borislav Petkov [bp@...en8.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.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/