Contribute
Register

Quick Guide to Generate a SSDT for CPU Power Management

Would you mind sharing what Clover did behind the scenes? Does it have anything to do with HWP? Personally speaking, I prefer HWP over EIST. HWP provides faster response and keep in lower states when idle.

If you look at your patchmatic -extract output, you will see the SSDT that Clover generated. Or you can view the SSDT in MaciASL (it is usually the last SSDT in the extract).

It is essentially the same content as SSDT-XCPM.dsl.
Nothing to do with HWP. HWP enablement is determined by SMBIOS in use, nothing else.
 
I didn't generate an SSDT since I use i7 8550u, my output in the terminal is in the next lines, but is something wrong with my IGPU or its normal those values?
Code:
CPU Ratio Info:
------------------------------------
CPU Low Frequency Mode.............: 400 MHz
CPU Maximum non-Turbo Frequency....: 2000 MHz
CPU Maximum Turbo Frequency........: 4000 MHz

IGPU Info:
------------------------------------
IGPU Current Frequency.............:    0 MHz
IGPU Minimum Frequency.............:  300 MHz
IGPU Maximum Non-Turbo Frequency...:  300 MHz
IGPU Maximum Turbo Frequency.......: 1150 MHz
IGPU Maximum limit.................: No Limit

CPU P-States [ (13) 27 37 ] iGPU P-States [ ]
CPU C3-Cores [ 0 2 5 ]
CPU P-States [ (13) 15 27 37 ] iGPU P-States [ ]
CPU C3-Cores [ 0 1 2 4 5 6 ]
CPU P-States [ (13) 15 18 27 37 ] iGPU P-States [ ]
CPU C3-Cores [ 0 1 2 3 4 5 6 7 ]
CPU P-States [ (13) 15 18 21 27 37 ] iGPU P-States [ ]
CPU P-States [ (13) 14 15 18 21 27 37 ] iGPU P-States [ ]
CPU P-States [ 13 14 15 18 (20) 21 24 27 37 ] iGPU P-States [ ]
CPU P-States [ (13) 14 15 18 19 20 21 24 27 37 ] iGPU P-States [ ]
CPU P-States [ 13 14 15 16 18 19 (20) 21 24 27 37 ] iGPU P-States [ ]
CPU P-States [ (13) 14 15 16 17 18 19 20 21 24 27 37 ] iGPU P-States [ ]

Edit:
I used the method with SSDT-XCPM.aml and now my output is this:
(It's finally correct? I have more P-States)

Code:
CPU Ratio Info:
------------------------------------
CPU Low Frequency Mode.............: 400 MHz
CPU Maximum non-Turbo Frequency....: 2000 MHz
CPU Maximum Turbo Frequency........: 4000 MHz

IGPU Info:
------------------------------------
IGPU Current Frequency.............:    0 MHz
IGPU Minimum Frequency.............:  300 MHz
IGPU Maximum Non-Turbo Frequency...:  300 MHz
IGPU Maximum Turbo Frequency.......: 1150 MHz
IGPU Maximum limit.................: No Limit

CPU P-States [ (13) 29 37 ] iGPU P-States [ ]
CPU C3-Cores [ 0 2 5 ]
CPU P-States [ 13 15 (20) 29 37 ] iGPU P-States [ ]
CPU C3-Cores [ 0 2 5 6 7 ]
CPU P-States [ (13) 14 15 20 29 37 ] iGPU P-States [ ]
CPU C3-Cores [ 0 2 3 4 5 6 7 ]
CPU P-States [ (13) 14 15 16 20 29 37 ] iGPU P-States [ ]
CPU P-States [ (13) 14 15 16 20 29 30 37 ] iGPU P-States [ ]
CPU C3-Cores [ 0 1 2 3 4 5 6 7 ]
CPU P-States [ 13 14 15 16 18 (20) 29 30 37 ] iGPU P-States [ ]
CPU P-States [ (13) 14 15 16 17 18 20 29 30 37 ] iGPU P-States [ ]
CPU P-States [ (13) 14 15 16 17 18 20 29 30 32 37 ] iGPU P-States [ ]
CPU P-States [ (13) 14 15 16 17 18 19 20 29 30 32 37 ] iGPU P-States [ ]
CPU P-States [ (13) 14 15 16 17 18 19 20 25 29 30 32 37 ] iGPU P-States [ ]
CPU P-States [ (13) 14 15 16 17 18 19 20 21 25 29 30 32 37 ] iGPU P-States [ ]
CPU P-States [ 13 14 15 16 17 18 19 20 21 (24) 25 29 30 32 37 ] iGPU P-States [ (24) ]
CPU P-States [ 13 14 15 16 17 18 19 (20) 21 24 25 29 30 32 37 ] iGPU P-States [ (18) 24 ]
CPU P-States [ 13 14 15 16 17 18 19 20 21 24 25 (26) 29 30 32 37 ] iGPU P-States [ (18) 24 ]
CPU P-States [ (13) 14 15 16 17 18 19 20 21 23 24 25 26 29 30 32 37 ] iGPU P-States [ 18 24 ]
CPU P-States [ 13 14 15 16 17 18 19 20 21 22 23 24 25 (26) 29 30 32 37 ] iGPU P-States [ 18 24 ]
CPU P-States [ 13 14 15 16 17 18 19 20 21 22 23 24 25 26 29 30 (31) 32 37 ] iGPU P-States [ 18 24 ]
CPU P-States [ 13 14 15 16 17 18 19 20 21 22 23 24 25 26 29 30 31 32 37 (40) ] iGPU P-States [ 18 24 ]
CPU P-States [ 13 14 15 16 17 18 19 20 21 22 23 24 25 26 29 30 31 32 33 (37) 40 ] iGPU P-States [ 18 24 ]
CPU P-States [ 13 14 15 16 17 18 19 20 21 22 23 24 25 26 29 30 31 32 33 (35) 37 40 ] iGPU P-States [ 18 24 ]
CPU P-States [ 13 14 15 16 17 18 19 20 21 22 23 24 25 26 29 30 31 32 33 35 36 (37) 40 ] iGPU P-States [ 18 24 ]
CPU P-States [ 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 35 36 (37) 40 ] iGPU P-States [ (18) 24 ]
CPU P-States [ 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 (34) 35 36 37 40 ] iGPU P-States [ 18 24 ]
CPU P-States [ (13) 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 40 ] iGPU P-States [ 18 24 ]
CPU P-States [ 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 (38) 40 ] iGPU P-States [ 18 24 ]

Not possible to determine any difference without PR files that represent both scenarios.

Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Use the gen_debug.sh tool mentioned in the FAQ, that way it is less likely you'll omit something.
 

Attachments

  • debug_6021.zip
    5.5 MB · Views: 98
Thanks for the quick reply.
Here is the file using gen_debug.sh in the FAQ

Why only one set of PR file attached?
You mentioned two different scenarios, didn't you?
Expect two sets of PR files, one for each scenario.
 
Why only one set of PR file attached?
You mentioned two different scenarios, didn't you?
Expect two sets of PR files, one for each scenario.

The 1st scenario was incomplete because I skipped one part of the tutorial by mistake, in my 2nd I did everything as it was supposed.
So, the PR files are from the 2nd scenario and according to the files, is everything working as expected?

P.s
I just noticed also, that I followed the tutorial bellow, but I made a reply in this topic by mistake.
https://www.tonymacx86.com/threads/guide-native-power-management-for-laptops.175801/
 
Last edited:
The 1st scenario was incomplete because I skipped one part of the tutorial by mistake, in my 2nd I did everything as it was supposed.
So, the PR files are from the 2nd scenario and according to the files, is everything working as expected?

P.s
I just noticed also, that I followed the tutorial bellow, but I made a reply in this topic by mistake.
https://www.tonymacx86.com/threads/guide-native-power-management-for-laptops.175801/

I still don't see where you attached PR files for the two separate scenarios.
 
If you look at your patchmatic -extract output, you will see the SSDT that Clover generated. Or you can view the SSDT in MaciASL (it is usually the last SSDT in the extract).

It is essentially the same content as SSDT-XCPM.dsl.
Nothing to do with HWP. HWP enablement is determined by SMBIOS in use, nothing else.
Since my build is 8700K, I choose the newly released Mac Mini as my model. It enables HWP. I wonder how these two power management cope with each other.
 
Since my build is 8700K, I choose the newly released Mac Mini as my model. It enables HWP. I wonder how these two power management cope with each other.

No "coping" required (no idea what you mean really).
 
No "coping" required (no idea what you mean really).
My question is who takes the charge for CPU power management if they both are enabled and working. With my past experience with Pentium G4600, you have to fake cpuid to 0306A0 and use NullIntelCPU to disable EIST completely so that HWP takes the charge here.
 
My question is who takes the charge for CPU power management if they both are enabled and working. With my past experience with Pentium G4600, you have to fake cpuid to 0306A0 and use NullIntelCPU to disable EIST completely so that HWP takes the charge here.

Certain plists in X86PlatformPlugin are HWP enabled.

Note: Just because HWP is a hardware controlled CPU PM mechanism, does not mean it cannot be tweaked/adjusted by software.
 
Back
Top