cpufreq: intel_pstate: Support HWP processors in all operation modes (eb5139d1) · Commits · 戴 / test

Currently, some processors supporting HWP are only supported by intel_pstate if HWP is actually going to be used and not supported otherwise which is confusing. Specifically, they are not supported if "intel_pstate=no_hwp" is passed to the kernel in the command line or if the driver is started in the passive mode ("intel_pstate=passive"). There is no real reason for that, because everything about those processor is known anyway and the driver can work with them in all modes, so make that happen, but use the load-based P-state selection algorithm for the active mode "powersave" policy with them. Signed-off-by:

Rafael J. Wysocki <rafael.j.wysocki@intel.com>

drivers/cpufreq/intel_pstate.c

+19 −14

Original line number	Diff line number	Diff line
		@@ -2627,19 +2627,23 @@ static const struct x86_cpu_id hwp_support_ids[] __initconst = {

		static int __init intel_pstate_init(void)
		{
		const struct x86_cpu_id *id;
		struct cpu_defaults *cpu_def;
		int rc = 0;
		int rc;

		if (no_load)
		return -ENODEV;

		if (x86_match_cpu(hwp_support_ids) && !no_hwp) {
		if (x86_match_cpu(hwp_support_ids)) {
		copy_cpu_funcs(&core_params.funcs);
		if (no_hwp) {
		pstate_funcs.get_target_pstate = get_target_pstate_use_cpu_load;
		} else {
		hwp_active++;
		intel_pstate.attr = hwp_cpufreq_attrs;
		goto hwp_cpu_matched;
		}
		} else {
		const struct x86_cpu_id *id;
		struct cpu_defaults *cpu_def;

		id = x86_match_cpu(intel_pstate_cpu_ids);
		if (!id)
		@@ -2649,6 +2653,7 @@ static int __init intel_pstate_init(void)

		copy_pid_params(&cpu_def->pid_policy);
		copy_cpu_funcs(&cpu_def->funcs);
		}

		if (intel_pstate_msrs_not_valid())
		return -ENODEV;

Admin message