Skip to contentSkip to conversation

AMD Bobcat cpufreq

DISCUSSION Joonas Saarinen 2 participants 2 messages Oct 18, 2013

lore
Share & tools
lore
#0 lore raw
Quoted 3 lines · Borislav Petkov [[email protected]] 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.

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.

Joonas

#1 lore raw
Quoted 14 lines · Joonas Saarinen
Quoted 3 lines · Borislav Petkov [[email protected]] 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:

Quoted 7 lines

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.

Quoted 3 lines

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.

Signature · 5 lines
Regards/Gruss,
    Boris.

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