But isn't this policy applied by the governor? I thought when I chose some governor that some very concrete policy (and algorithm) would be applied. Can I assume that in this case the govenors aren't used anymore? It also says that "What those hints are depends on which P-state selection algorithm has been applied to the given policy". In the docs it says in "active mode with HWP intel_pstate relies on the processor to select P-states by itself".
#HACKINTOOL ENABLE HWP DRIVER#
Regading the driver modus operandi I'm not sure I quite understand it's behaviour when HWP is enabled. But I only have the following attributes under intel_pstate directory and I'm not sure what kind of tweak I could do that would reveal HWP behaviour - max_perf_pct, min_perf_pct, no_turbo, num_pstates and turbo_pct. Like tweaking sysfs parameters and watching for system response. It would be great to have method that could hint on the HWP usage.
Having no kernel options that could disable HWP (like intel_pstate=no_hwp) and neither BIOS options conflicting with HWP usage, I'me forced to admit that it must enabled. AFAIK, HWP is the default method since kernel 4.6-rc1 (see commit ). Processors.CPUFrequencyLimits=Full turbo uplift Processors.UPILinkFrequency=Max Performance
#HACKINTOOL ENABLE HWP PLUS#
Processors.SnoopPreference=Home Snoop Plus Processors.UPILinkDisable=Enable All Links Processors.IntelVirtualizationTechnology=Enable Processors.TrustedExecutionTechnology=Disable I do not see any configuration that might be disabling HWP on my system : My delay on this response was due to having access to BIOS parameters.īellow are the BIOS parameters for my system regarding the processor unit. This same behavior is observed in two different machines with the following CPU's - Xeon(R) Gold 6154, Core(TM) i7-6700HQ I am not an expert on the subject and that's why I post this question. The attribute status which could give a hint is also not present in /sys/devices/system/cpu/intel_pstate/ (see guide - section global attributes) And why are the energy_preference parameters not available in sysfs? I find it a bit awkward that intel_state is not using HWP, since it is the default behavior and that there are no kernel parameters telling him to do otherwise. If it works in this mode, the scaling_driver policy attribute in sysfs for all CPUFreq policies contains the string “intel_pstate”. This is the default operation mode of intel_pstate. On the other hand, the scaling_driver attribute has the value intel_pstate, so once again by guide - section active-mode I can assume intel_pstate is set in active mode. If intel_pstate works in the active mode with the HWP feature enabled in the processor, additional attributes are present in every CPUFreq policy directory in sysfsīut those attributes (energy_performance_preference and energy_performance_available_preferences) are not present in sysfs. Namely I can see:įrom the guide - section energy-vs-performance-hints I can read that: I wonder IF intel_pstate is working in active_mode with OR without HWP enabled? I believe the processor supports HWP because as I can see 4 HWP flags when I cat /proc/cpuinfo.
0 kommentar(er)
