[Intel] Overclocking bins with unlocked K processors [Experimental]

[cyring]

Commit db15a83 displays the frequency ratio bins of unlocked processors. Usually the K series.

• Frequency and ratio bins are presented as relative values
  Those are read from MSR_FLEX_RATIO

• OC capability is shown in Technologies
OC_ENABLED bit(29) from CAPID_B CSR register at offset 0xE8

---

A non K processor will display as below

• Uncapable OC

• No Overclock section within Processor window

[cyring]

@rushvora @olejon @BugReporterZ @justanerd and anyone with an unlocked Intel processor

Based on develop branch, can you please show me the results of the above ?

Remark: because MSR FLEX is poorly documented, you have to activate the experimental mode while driver is starting

insmod corefreqk.ko Experimental=1

Any processor with successful access will be marked for feature production in next commits

[BugReporterZ]

This is what I'm seeing:

[cyring]

Thanks a lot, I will add this processor to the granted list.

In case you have other Intel architectures, can you show me results ?

[cyring]

Some legacy Xeon appear to have a OC ratio within MSR_FLEX_RATIO but at different bits field named CLOCK_FLEX_MAX[12-8]

Right after booting, the MSR_FLEX_RATIO with my Xeon W3690 is zeroed but I noticed than I can write a certain bits pattern, thus CLOCK_FLEX_MAX

wrmsr 0x194 0x10400
rdmsr -a 0x194
10400
10400
10400
10400
10400
10400
10400
10400
10400
10400
10400
10400

Here is the result:

The function has been improved with two methods:
One made for legacy architectures; the second for recent processors.

@BugReporterZ Can you please tell if you are still reading the same results since commit f622261

[BugReporterZ]

I see this after rebuilding:

[cyring]

I have reverted the changes in commit 332dbda because too many UI impacts and it was not solving for your issue.

[cyring]

@BugReporterZ Hello

In commit 9b644fd you can now build with the constraints UI_RULER_MINIMUM and UI_RULER_MAXIMUM

• For example:

make -j UI_RULER_MAXIMUM=50 UI_RULER_MINIMUM=5

[BugReporterZ]

It appears to work—for the screenshot below I defined a maximum of 55 and it seems to be respecting that:

[cyring]

Thank you for your return