Real Temp - New temp program for Intel Core processors

[some_one]

Wow, where to start. First I guess is to say thank you to Franck for replying and discussing the above. Much appreciated.

(on NHM, each core can use a different multiplier).

Just to clarify, I hope you don't mean at the same time here.

So, if you want to report turbo mode clock speed of NHM, you need to use duty cycles. That generates lot of problems.

I don't understand why it has to be so difficult. There are two performance registers for each thread/core that will give the average ratio over time, say every 0.5 seconds. This should take little cycles to achieve and I would expect it have negligible effect on the result.

TMonitor does compute duty clock speed as well, based on the same Intel method (same regs to say it all), but uses a modified algo that does not change the cores activity.

If the core is idle in one of the higher c-states you will need to wake it to read those registers. Does it not then switch to the package performance state whatever that may be at that time?

However when I disable EIST/C states, duty clock speed will then NOT EQUAL physical clock speedith.

No. If you disable c-states the duty cycle will be 100% therefore equal the physical clock. If you look at your previous ss you haven't fully disabled c-states. If you had C0% would read 100% all the time.


With the Intel method if the core were active for only 1% of the time but for that 1% it was at 21x multi then that's what would show as the multi but it seems your saying TMonitor will reduce that figure because of the small percentage of time that it's been available. Or maybe I've misunderstood.