amd-pstate cleanups
Subsystems (4)
v3 cover amd-pstate cleanups
From: Mario Limonciello <[email protected]>
This series overhauls locking and drops many unnecessarily cached variables.
Debugging messages are also dropped in favor of more ftracing.
This series is based off superm1/linux.git bleeding-edge branch.
v2->v3:
* Mostly pick up tags
* Add new patch 1/18 that fixes a KBZ issue (see patch for detail)
* Fixup for min_freq issue in dropping cached values patch
* Fixup for unit tests to only run on online CPUs
Mario Limonciello (18):
cpufreq/amd-pstate: Invalidate cppc_req_cached during suspend cpufreq/amd-pstate: Show a warning when a CPU fails to setup cpufreq/amd-pstate: Drop min and max cached frequencies cpufreq/amd-pstate: Move perf values into a union cpufreq/amd-pstate: Overhaul locking
cpufreq/amd-pstate: Drop cppc_cap1_cached cpufreq/amd-pstate-ut: Use _free macro to free put policy cpufreq/amd-pstate-ut: Allow lowest nonlinear and lowest to be the
same
cpufreq/amd-pstate-ut: Drop SUCCESS and FAIL enums cpufreq/amd-pstate-ut: Run on all of the correct CPUs cpufreq/amd-pstate-ut: Adjust variable scope for
amd_pstate_ut_check_freq()
cpufreq/amd-pstate: Replace all AMD_CPPC_* macros with masks cpufreq/amd-pstate: Cache CPPC request in shared mem case too cpufreq/amd-pstate: Move all EPP tracing into *_update_perf and
*_set_epp functions
cpufreq/amd-pstate: Update cppc_req_cached for shared mem EPP writes cpufreq/amd-pstate: Drop debug statements for policy setting cpufreq/amd-pstate: Rework CPPC enabling cpufreq/amd-pstate: Stop caching EPP
arch/x86/include/asm/msr-index.h | 20 +- arch/x86/kernel/acpi/cppc.c | 4 +- drivers/cpufreq/amd-pstate-trace.h | 13 +- drivers/cpufreq/amd-pstate-ut.c | 209 +++++----- drivers/cpufreq/amd-pstate.c | 592 ++++++++++++++--------------- drivers/cpufreq/amd-pstate.h | 61 +-- 6 files changed, 428 insertions(+), 471 deletions(-)
Signature · 1 line
2.43.0
PATCH v3 1/18 cpufreq/amd-pstate: Invalidate cppc_req_cached during suspend
From: Mario Limonciello <[email protected]>
During resume it's possible the firmware didn't restore the CPPC request MSR but the kernel thinks the values line up. This leads to incorrect performance after resume from suspend.
To fix the issue invalidate the cached value at suspend. During resume use the saved values programmed as cached limits.
--- drivers/cpufreq/amd-pstate.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/cpufreq/amd-pstate.c +4 -1
@@ -1611,7 +1611,7 @@ static int amd_pstate_epp_reenable(struct cpufreq_policy *policy) max_perf, policy->boost_enabled); } -return amd_pstate_update_perf (cpudata,0 ,0 , max_perf, cpudata->epp_cached, false); +return amd_pstate_epp_update_limit (policy); }static int amd_pstate_epp_cpu_online (struct cpufreq_policy *policy)
@@ -1660,6 +1660,9 @@ static int amd_pstate_epp_suspend(struct cpufreq_policy *policy)if (cppc_state !=AMD_PSTATE_ACTIVE )return 0 ; +/* invalidate to ensure it's rewritten during resume */ + cpudata->cppc_req_cached =0 ; +/* set this flag to avoid setting core offline*/ cpudata->suspended = true;
Signature · 1 line
2.43.0
Re: [PATCH v3 01/18] cpufreq/amd-pstate: Invalidate cppc_req_cached during suspend
Hello Mario,
Quoted 21 lines · Mario Limonciello
From: Mario Limonciello <[email protected]>
During resume it's possible the firmware didn't restore the CPPC request MSR but the kernel thinks the values line up. This leads to incorrect performance after resume from suspend.
To fix the issue invalidate the cached value at suspend. During resume use the saved values programmed as cached limits.
Reported-by Miroslav Pavleski <[email protected]>Signed-off-by Mario Limonciello <[email protected]>--- drivers/cpufreq/amd-pstate.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)drivers/cpufreq/amd-pstate.c +0
-0
drivers/cpufreq/amd-pstate.c static int amd_pstate_epp_reenable(struct cpufreq_policy *policy) · line 1612
Quoted 2 lines
drivers/cpufreq/amd-pstate.c +0
-0@@ -1611,7 +1611,7 @@ static int amd_pstate_epp_reenable(struct cpufreq_policy *policy) max_perf, policy->boost_enabled); }
You can also remove the tracing code from amd_pstate_epp_reenable(), i.e,
if (trace_amd_pstate_epp_perf_enabled()) {
trace_amd_pstate_epp_perf(cpudata->cpu, cpudata->highest_perf,
cpudata->epp_cached,
FIELD_GET(AMD_CPPC_MIN_PERF_MASK, cpudata->cppc_req_cached),
max_perf, policy->boost_enabled);
}Since amd_pstate_epp_update_limit() also has the the tracing code.
The patch looks good to me otherwise.
Signature · 2 lines
Thanks and Regards gautham.
Quoted 19 lines
drivers/cpufreq/amd-pstate.c +4
-1-return amd_pstate_update_perf (cpudata,0 ,0 , max_perf, cpudata->epp_cached, false); +return amd_pstate_epp_update_limit (policy); }static int amd_pstate_epp_cpu_online (struct cpufreq_policy *policy)@@ -1660,6 +1660,9 @@ static int amd_pstate_epp_suspend(struct cpufreq_policy *policy)if (cppc_state !=AMD_PSTATE_ACTIVE )return 0 ; +/* invalidate to ensure it's rewritten during resume */ + cpudata->cppc_req_cached =0 ; +/* set this flag to avoid setting core offline*/ cpudata->suspended = true;Signature · 1 line
2.43.0
Re: [PATCH v3 01/18] cpufreq/amd-pstate: Invalidate cppc_req_cached during suspend
Quoted 30 lines · Gautham R. Shenoy
Hello Mario,
Quoted 21 lines · Mario Limonciello
From: Mario Limonciello <[email protected]>
During resume it's possible the firmware didn't restore the CPPC request MSR but the kernel thinks the values line up. This leads to incorrect performance after resume from suspend.
To fix the issue invalidate the cached value at suspend. During resume use the saved values programmed as cached limits.
Reported-by Miroslav Pavleski <[email protected]>Signed-off-by Mario Limonciello <[email protected]>--- drivers/cpufreq/amd-pstate.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)drivers/cpufreq/amd-pstate.c +0
-0drivers/cpufreq/amd-pstate.c static int amd_pstate_epp_reenable(struct cpufreq_policy *policy) · line 1612
Quoted 2 lines
drivers/cpufreq/amd-pstate.c +0
-0@@ -1611,7 +1611,7 @@ static int amd_pstate_epp_reenable(struct cpufreq_policy *policy) max_perf, policy->boost_enabled); }You can also remove the tracing code from
amd_pstate_epp_reenable(), i.e,
Quoted 8 lines
if (trace_amd_pstate_epp_perf_enabled()) { trace_amd_pstate_epp_perf(cpudata->cpu, cpudata->highest_perf, cpudata->epp_cached, FIELD_GET(AMD_CPPC_MIN_PERF_MASK, cpudata->cppc_req_cached), max_perf, policy->boost_enabled); }Since
amd_pstate_epp_update_limit()also has the the tracing code.
Yeah; the tracing code gets updated later in the series.
My plan is this commit is a minimal fix, and will go to 6.14, the rest will be in 6.15.
Quoted 5 lines
The patch looks good to me otherwise.
Reviewed-by Gautham R. Shenoy <[email protected]>
Thanks!
Re: [PATCH v3 01/18] cpufreq/amd-pstate: Invalidate cppc_req_cached during suspend
In reply to Mario LimoncielloQuoted 21 lines · Mario Limonciello
From: Mario Limonciello <[email protected]>
During resume it's possible the firmware didn't restore the CPPC request MSR but the kernel thinks the values line up. This leads to incorrect performance after resume from suspend.
To fix the issue invalidate the cached value at suspend. During resume use the saved values programmed as cached limits.
Reported-by Miroslav Pavleski <[email protected]>Signed-off-by Mario Limonciello <[email protected]>--- drivers/cpufreq/amd-pstate.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)drivers/cpufreq/amd-pstate.c +0
-0
drivers/cpufreq/amd-pstate.c static int amd_pstate_epp_reenable(struct cpufreq_policy *policy) · line 1614
Quoted 5 lines
drivers/cpufreq/amd-pstate.c +1
-1@@ -1611,7 +1611,7 @@ static int amd_pstate_epp_reenable(struct cpufreq_policy *policy) max_perf, policy->boost_enabled); } -return amd_pstate_update_perf (cpudata,0 ,0 , max_perf, cpudata->epp_cached, false); +return amd_pstate_epp_update_limit (policy);
Can we also add the check "if (policy->min != cpudata->min_limit_freq || policy->max != cpudata->max_limit_freq)" in "amd_pstate_epp_update_limit()" before calling "amd_pstate_update_min_max_limit()". I think it would help in avoiding some unnecessary calls to the update_min_max_limit() function.
Patch looks good to me otherwise.
Thanks,
Dhananjay
Quoted 13 lines
drivers/cpufreq/amd-pstate.c +3
-0}static int amd_pstate_epp_cpu_online (struct cpufreq_policy *policy)@@ -1660,6 +1660,9 @@ static int amd_pstate_epp_suspend(struct cpufreq_policy *policy)if (cppc_state !=AMD_PSTATE_ACTIVE )return 0 ; +/* invalidate to ensure it's rewritten during resume */ + cpudata->cppc_req_cached =0 ; +/* set this flag to avoid setting core offline*/ cpudata->suspended = true;
Dhananjay Ugwekar
Reviewed-byRe: [PATCH v3 01/18] cpufreq/amd-pstate: Invalidate cppc_req_cached during suspend
Quoted 25 lines · Dhananjay Ugwekar
Quoted 24 lines · Mario Limonciello
From: Mario Limonciello <[email protected]>
During resume it's possible the firmware didn't restore the CPPC request MSR but the kernel thinks the values line up. This leads to incorrect performance after resume from suspend.
To fix the issue invalidate the cached value at suspend. During resume use the saved values programmed as cached limits.
Reported-by Miroslav Pavleski <[email protected]>Signed-off-by Mario Limonciello <[email protected]>--- drivers/cpufreq/amd-pstate.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)drivers/cpufreq/amd-pstate.c +0
-0@@ -1611,7 +1611,7 @@ static int amd_pstate_epp_reenable(struct cpufreq_policy *policy) max_perf, policy->boost_enabled); }
Quoted 6 lines
drivers/cpufreq/amd-pstate.c static int amd_pstate_epp_reenable(struct cpufreq_policy *policy) · line 1614
Quoted 2 lines
drivers/cpufreq/amd-pstate.c +1
-1-return amd_pstate_update_perf (cpudata,0 ,0 , max_perf, cpudata->epp_cached, false); +return amd_pstate_epp_update_limit (policy);Can we also add the check "if (
policy->min!=cpudata->min_limit_freq||policy->max!=cpudata->max_limit_freq)" in "amd_pstate_epp_update_limit()" before calling "amd_pstate_update_min_max_limit()". I think it would help in avoiding some unnecessary calls to theupdate_min_max_limit()function.
You can ignore this, I see that you have handled it in the 3rd patch.
Quoted 20 lines
Patch looks good to me otherwise.
Thanks,
DhananjayQuoted 13 lines
drivers/cpufreq/amd-pstate.c +3
-0}static int amd_pstate_epp_cpu_online (struct cpufreq_policy *policy)@@ -1660,6 +1660,9 @@ static int amd_pstate_epp_suspend(struct cpufreq_policy *policy)if (cppc_state !=AMD_PSTATE_ACTIVE )return 0 ; +/* invalidate to ensure it's rewritten during resume */ + cpudata->cppc_req_cached =0 ; +/* set this flag to avoid setting core offline*/ cpudata->suspended = true;
PATCH v3 2/18 cpufreq/amd-pstate: Show a warning when a CPU fails to setup
In reply to Mario LimoncielloFrom: Mario Limonciello <[email protected]>
I came across a system that MSR_AMD_CPPC_CAP1 for some CPUs isn't populated. This is an unexpected behavior that is most likely a BIOS bug. In the event it happens I'd like users to report bugs to properly root cause and get this fixed.
--- drivers/cpufreq/amd-pstate.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/cpufreq/amd-pstate.c +2 -0
@@ -1034,6 +1034,7 @@ static int amd_pstate_cpu_init(struct cpufreq_policy *policy) free_cpudata2:freq_qos_remove_request (&cpudata->req[0 ]); free_cpudata1: +pr_warn ("Failed to initialize CPU %d: %d\n" , policy->cpu, ret);kfree (cpudata);return ret; }
@@ -1527,6 +1528,7 @@ static int amd_pstate_epp_cpu_init(struct cpufreq_policy *policy)return 0 ; free_cpudata1: +pr_warn ("Failed to initialize CPU %d: %d\n" , policy->cpu, ret);kfree (cpudata);return ret; }
Signature · 1 line
2.43.0
Re: [PATCH v3 02/18] cpufreq/amd-pstate: Show a warning when a CPU fails to setup
Quoted 8 lines · Mario Limonciello
From: Mario Limonciello <[email protected]>
I came across a system that
MSR_AMD_CPPC_CAP1for some CPUs isn't populated. This is an unexpected behavior that is most likely a BIOS bug. In the event it happens I'd like users to report bugs to properly root cause and get this fixed.Reviewed-by Gautham R. Shenoy <[email protected]>
Quoted 25 lines
Signed-off-by Mario Limonciello <[email protected]>--- drivers/cpufreq/amd-pstate.c | 2 ++ 1 file changed, 2 insertions(+)drivers/cpufreq/amd-pstate.c +2
-0@@ -1034,6 +1034,7 @@ static int amd_pstate_cpu_init(struct cpufreq_policy *policy) free_cpudata2:freq_qos_remove_request (&cpudata->req[0 ]); free_cpudata1: +pr_warn ("Failed to initialize CPU %d: %d\n" , policy->cpu, ret);kfree (cpudata);return ret; }@@ -1527,6 +1528,7 @@ static int amd_pstate_epp_cpu_init(struct cpufreq_policy *policy)return 0 ; free_cpudata1: +pr_warn ("Failed to initialize CPU %d: %d\n" , policy->cpu, ret);kfree (cpudata);return ret; }
PATCH v3 3/18 cpufreq/amd-pstate: Drop min and max cached frequencies
In reply to Mario LimoncielloFrom: Mario Limonciello <[email protected]>
Use the perf_to_freq helpers to calculate this on the fly.
--
v3:
* Fix calc error for min_freq
v2:
* Keep cached limits
--- drivers/cpufreq/amd-pstate-ut.c | 14 +++---- drivers/cpufreq/amd-pstate.c | 70 +++++++++++---------------------- drivers/cpufreq/amd-pstate.h | 9 +---- 3 files changed, 32 insertions(+), 61 deletions(-)
drivers/cpufreq/amd-pstate-ut.c +7 -7
@@ -214,14 +214,14 @@ static void amd_pstate_ut_check_freq(u32 index)break ; cpudata = policy->driver_data; -if (!((cpudata->max_freq >= cpudata->nominal_freq) && +if (!((policy->cpuinfo.max_freq >= cpudata->nominal_freq) && (cpudata->nominal_freq > cpudata->lowest_nonlinear_freq) && - (cpudata->lowest_nonlinear_freq > cpudata->min_freq) && - (cpudata->min_freq >0 ))) { + (cpudata->lowest_nonlinear_freq > policy->cpuinfo.min_freq) && + (policy->cpuinfo.min_freq >0 ))) { amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s cpu%d max=%d >= nominal=%d > lowest_nonlinear=%d > min=%d > 0, the formula is incorrect!\n" , - __func__, cpu, cpudata->max_freq, cpudata->nominal_freq, - cpudata->lowest_nonlinear_freq, cpudata->min_freq); + __func__, cpu, policy->cpuinfo.max_freq, cpudata->nominal_freq, + cpudata->lowest_nonlinear_freq, policy->cpuinfo.min_freq); goto skip_test; }
@@ -233,13 +233,13 @@ static void amd_pstate_ut_check_freq(u32 index) }if (cpudata->boost_supported) { -if ((policy->max == cpudata->max_freq) || +if ((policy->max == policy->cpuinfo.max_freq) || (policy->max == cpudata->nominal_freq)) amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_PASS ;else { amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s cpu%d policy_max=%d should be equal cpu_max=%d or cpu_nominal=%d !\n" , - __func__, cpu, policy->max, cpudata->max_freq, + __func__, cpu, policy->max, policy->cpuinfo.max_freq, cpudata->nominal_freq); goto skip_test; }
drivers/cpufreq/amd-pstate.c +23 -47
162 lines not on this page · raw message
drivers/cpufreq/amd-pstate.h +2 -7
@@ -46,8 +46,6 @@ struct amd_aperf_mperf {* @max_limit_perf: Cached value of the performance corresponding to policy->max * @min_limit_freq: Cached value of policy->min (in khz) * @max_limit_freq: Cached value of policy->max (in khz) -* @max_freq: the frequency (in khz) that mapped to highest_perf -* @min_freq: the frequency (in khz) that mapped to lowest_perf * @nominal_freq: the frequency (in khz) that mapped to nominal_perf * @lowest_nonlinear_freq: the frequency (in khz) that mapped to lowest_nonlinear_perf * @cur: Difference of Aperf/Mperf/tsc count between last and current sample
@@ -77,11 +75,8 @@ struct amd_cpudata {u8 prefcore_ranking;u8 min_limit_perf;u8 max_limit_perf; -u32 min_limit_freq; -u32 max_limit_freq; - -u32 max_freq; -u32 min_freq; +u32 min_limit_freq; +u32 max_limit_freq;u32 nominal_freq;u32 lowest_nonlinear_freq;
Signature · 1 line
2.43.0
Re: [PATCH v3 03/18] cpufreq/amd-pstate: Drop min and max cached frequencies
Quoted 5 lines · Mario Limonciello
From: Mario Limonciello <[email protected]>
Use the
perf_to_freqhelpers to calculate this on the fly.Signed-off-by Mario Limonciello <[email protected]>
LGTM.
Signature · 2 lines
Thanks and Regards gautham.
Re: [PATCH v3 03/18] cpufreq/amd-pstate: Drop min and max cached frequencies
In reply to Mario LimoncielloQuoted 3 lines · Mario Limonciello
From: Mario Limonciello <[email protected]>
Use the
perf_to_freqhelpers to calculate this on the fly.
Can we call out the below change (in the -1550,7 +1525,8 code chunk) in the commit message, or split it out to different patch
* Adding the if check in amd_pstate_epp_update_limit()
Quoted 3 lines
Signed-off-by Mario Limonciello <[email protected]>--
We need one more hyphen here I think i.e."---", otherwise the version info is showing up in the commit message
Quoted 88 lines
v3:
* Fix calc error formin_freq
v2:
* Keep cached limits--- drivers/cpufreq/amd-pstate-ut.c | 14 +++---- drivers/cpufreq/amd-pstate.c | 70 +++++++++++---------------------- drivers/cpufreq/amd-pstate.h | 9 +---- 3 files changed, 32 insertions(+), 61 deletions(-)drivers/cpufreq/amd-pstate-ut.c +7
-7@@ -214,14 +214,14 @@ static void amd_pstate_ut_check_freq(u32 index)break ; cpudata = policy->driver_data; -if (!((cpudata->max_freq >= cpudata->nominal_freq) && +if (!((policy->cpuinfo.max_freq >= cpudata->nominal_freq) && (cpudata->nominal_freq > cpudata->lowest_nonlinear_freq) && - (cpudata->lowest_nonlinear_freq > cpudata->min_freq) && - (cpudata->min_freq >0 ))) { + (cpudata->lowest_nonlinear_freq > policy->cpuinfo.min_freq) && + (policy->cpuinfo.min_freq >0 ))) { amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s cpu%d max=%d >= nominal=%d > lowest_nonlinear=%d > min=%d > 0, the formula is incorrect!\n" , - __func__, cpu, cpudata->max_freq, cpudata->nominal_freq, - cpudata->lowest_nonlinear_freq, cpudata->min_freq); + __func__, cpu, policy->cpuinfo.max_freq, cpudata->nominal_freq, + cpudata->lowest_nonlinear_freq, policy->cpuinfo.min_freq); goto skip_test; }@@ -233,13 +233,13 @@ static void amd_pstate_ut_check_freq(u32 index) }if (cpudata->boost_supported) { -if ((policy->max == cpudata->max_freq) || +if ((policy->max == policy->cpuinfo.max_freq) || (policy->max == cpudata->nominal_freq)) amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_PASS ;else { amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s cpu%d policy_max=%d should be equal cpu_max=%d or cpu_nominal=%d !\n" , - __func__, cpu, policy->max, cpudata->max_freq, + __func__, cpu, policy->max, policy->cpuinfo.max_freq, cpudata->nominal_freq); goto skip_test; }drivers/cpufreq/amd-pstate.c +2
-9@@ -717,7 +717,7 @@ static int amd_pstate_cpu_boost_update(struct cpufreq_policy *policy, bool on)int ret =0 ; nominal_freq =READ_ONCE (cpudata->nominal_freq); - max_freq =READ_ONCE (cpudata->max_freq); + max_freq =perf_to_freq (cpudata,READ_ONCE (cpudata->highest_perf));if (on) policy->cpuinfo.max_freq = max_freq;@@ -901,35 +901,26 @@ static u32 amd_pstate_get_transition_latency(unsigned int cpu)static int amd_pstate_init_freq (struct amd_cpudata *cpudata) {int ret; -u32 min_freq, max_freq; -u32 nominal_freq, lowest_nonlinear_freq; +u32 min_freq, nominal_freq, lowest_nonlinear_freq;struct cppc_perf_caps cppc_perf; ret =cppc_get_perf_caps (cpudata->cpu, &cppc_perf);if (ret)return ret; -if (quirks && quirks->lowest_freq) - min_freq = quirks->lowest_freq; -else - min_freq = cppc_perf.lowest_freq; -if (quirks && quirks->nominal_freq) nominal_freq = quirks->nominal_freq;else nominal_freq = cppc_perf.nominal_freq; - min_freq *=1000 ; nominal_freq *=1000 ;
drivers/cpufreq/amd-pstate.c static u32 amd_pstate_get_transition_latency(unsigned int cpu) · line 919
Quoted 10 lines
drivers/cpufreq/amd-pstate.c +1
-7-WRITE_ONCE (cpudata->nominal_freq, nominal_freq); -WRITE_ONCE (cpudata->min_freq, min_freq); - - max_freq =perf_to_freq (cpudata, cpudata->highest_perf); - lowest_nonlinear_freq =perf_to_freq (cpudata, cpudata->lowest_nonlinear_perf); -WRITE_ONCE (cpudata->lowest_nonlinear_freq, lowest_nonlinear_freq); -WRITE_ONCE (cpudata->max_freq, max_freq); +if (quirks && quirks->lowest_freq) {
We can avoid the "{" for single line if statement, to keep checkpatch happy
drivers/cpufreq/amd-pstate.c static u32 amd_pstate_get_transition_latency(unsigned int cpu) · line 923
Quoted 4 lines
drivers/cpufreq/amd-pstate.c +4
-0+ min_freq = quirks->lowest_freq; + }else + min_freq = cppc_perf.lowest_freq; + min_freq *=1000 ;
I see that this min_freq part of the code is unchanged, just moved few lines below. If the moving is unintended can we avoid it, so that the diff is optimal.
drivers/cpufreq/amd-pstate.c static int amd_pstate_init_freq(struct amd_cpudata *cpudata) · line 940
Quoted 8 lines
drivers/cpufreq/amd-pstate.c +0
-1/** * Below values need to be initialized correctly, otherwise driver will fail to load @@ -937,12 +928,15 @@ static int amd_pstate_init_freq(struct amd_cpudata *cpudata)* lowest_nonlinear_freq is a value between [min_freq, nominal_freq] * Check _CPC in ACPI table objects if any values are incorrect */ -if (min_freq <=0 || max_freq <=0 || nominal_freq <=0 || min_freq > max_freq) {
Shouldn't we retain these sanity checks for min_freq and max_freq?
Thanks,
Dhananjay
Quoted 143 lines
drivers/cpufreq/amd-pstate.c +16
-30-pr_err ("min_freq(%d) or max_freq(%d) or nominal_freq(%d) value is incorrect\n" , - min_freq, max_freq, nominal_freq); +if (nominal_freq <=0 ) { +pr_err ("nominal_freq(%d) value is incorrect\n" , + nominal_freq);return -EINVAL ; } + lowest_nonlinear_freq =perf_to_freq (cpudata, cpudata->lowest_nonlinear_perf); +WRITE_ONCE (cpudata->lowest_nonlinear_freq, lowest_nonlinear_freq); +if (lowest_nonlinear_freq <= min_freq || lowest_nonlinear_freq > nominal_freq) {pr_err ("lowest_nonlinear_freq(%d) value is out of range [min_freq(%d), nominal_freq(%d)]\n" , lowest_nonlinear_freq, min_freq, nominal_freq);@@ -954,9 +948,9 @@ static int amd_pstate_init_freq(struct amd_cpudata *cpudata)static int amd_pstate_cpu_init (struct cpufreq_policy *policy) { -int min_freq, max_freq, ret; -struct device *dev;struct amd_cpudata *cpudata; +struct device *dev; +int ret;/* * Resetting PERF_CTL_MSR will put the CPU in P0 frequency, @@ -987,17 +981,11 @@ static int amd_pstate_cpu_init(struct cpufreq_policy *policy)if (ret) goto free_cpudata1; - min_freq =READ_ONCE (cpudata->min_freq); - max_freq =READ_ONCE (cpudata->max_freq); - policy->cpuinfo.transition_latency =amd_pstate_get_transition_latency (policy->cpu); policy->transition_delay_us =amd_pstate_get_transition_delay_us (policy->cpu); - policy->min = min_freq; - policy->max = max_freq; - - policy->cpuinfo.min_freq = min_freq; - policy->cpuinfo.max_freq = max_freq; + policy->cpuinfo.min_freq = policy->min =perf_to_freq (cpudata, cpudata->lowest_perf); + policy->cpuinfo.max_freq = policy->max =perf_to_freq (cpudata, cpudata->highest_perf); policy->boost_enabled =READ_ONCE (cpudata->boost_supported);@@ -1021,9 +1009,6 @@ static int amd_pstate_cpu_init(struct cpufreq_policy *policy) goto free_cpudata2; } - cpudata->max_limit_freq = max_freq; - cpudata->min_limit_freq = min_freq; - policy->driver_data = cpudata;if (!current_pstate_driver->adjust_perf)@@ -1081,14 +1066,10 @@ static int amd_pstate_cpu_suspend(struct cpufreq_policy *policy)static ssize_t show_amd_pstate_max_freq (struct cpufreq_policy *policy,char *buf) { -int max_freq;struct amd_cpudata *cpudata = policy->driver_data; - max_freq =READ_ONCE (cpudata->max_freq); -if (max_freq <0 ) -return max_freq; -return sysfs_emit (buf,"%u\n" , max_freq); +return sysfs_emit (buf,"%u\n" ,perf_to_freq (cpudata,READ_ONCE (cpudata->highest_perf))); } static ssize_t show_amd_pstate_lowest_nonlinear_freq(struct cpufreq_policy *policy,@@ -1446,10 +1427,10 @@ static bool amd_pstate_acpi_pm_profile_undefined(void)static int amd_pstate_epp_cpu_init (struct cpufreq_policy *policy) { -int min_freq, max_freq, ret;struct amd_cpudata *cpudata;struct device *dev;u64 value; +int ret;/* * Resetting PERF_CTL_MSR will put the CPU in P0 frequency, @@ -1480,19 +1461,13 @@ static int amd_pstate_epp_cpu_init(struct cpufreq_policy *policy)if (ret) goto free_cpudata1; - min_freq =READ_ONCE (cpudata->min_freq); - max_freq =READ_ONCE (cpudata->max_freq); - - policy->cpuinfo.min_freq = min_freq; - policy->cpuinfo.max_freq = max_freq; + policy->cpuinfo.min_freq = policy->min =perf_to_freq (cpudata, cpudata->lowest_perf); + policy->cpuinfo.max_freq = policy->max =perf_to_freq (cpudata, cpudata->highest_perf);/* It will be updated by governor */ policy->cur = policy->cpuinfo.min_freq; policy->driver_data = cpudata; - policy->min = policy->cpuinfo.min_freq; - policy->max = policy->cpuinfo.max_freq; - policy->boost_enabled =READ_ONCE (cpudata->boost_supported);/* @@ -1550,7 +1525,8 @@ static int amd_pstate_epp_update_limit(struct cpufreq_policy *policy)struct amd_cpudata *cpudata = policy->driver_data;u8 epp; -amd_pstate_update_min_max_limit (policy); +if (policy->min != cpudata->min_limit_freq || policy->max != cpudata->max_limit_freq) +amd_pstate_update_min_max_limit (policy);if (cpudata->policy ==CPUFREQ_POLICY_PERFORMANCE ) epp =0 ;drivers/cpufreq/amd-pstate.h +2
-7@@ -46,8 +46,6 @@ struct amd_aperf_mperf {* @max_limit_perf: Cached value of the performance corresponding to policy->max * @min_limit_freq: Cached value of policy->min (in khz) * @max_limit_freq: Cached value of policy->max (in khz) -* @max_freq: the frequency (in khz) that mapped to highest_perf -* @min_freq: the frequency (in khz) that mapped to lowest_perf * @nominal_freq: the frequency (in khz) that mapped to nominal_perf * @lowest_nonlinear_freq: the frequency (in khz) that mapped to lowest_nonlinear_perf * @cur: Difference of Aperf/Mperf/tsc count between last and current sample @@ -77,11 +75,8 @@ struct amd_cpudata {u8 prefcore_ranking;u8 min_limit_perf;u8 max_limit_perf; -u32 min_limit_freq; -u32 max_limit_freq; - -u32 max_freq; -u32 min_freq; +u32 min_limit_freq; +u32 max_limit_freq;u32 nominal_freq;u32 lowest_nonlinear_freq;
Re: [PATCH v3 03/18] cpufreq/amd-pstate: Drop min and max cached frequencies
Quoted 10 lines · Dhananjay Ugwekar
Quoted 3 lines · Mario Limonciello
From: Mario Limonciello <[email protected]>
Use the
perf_to_freqhelpers to calculate this on the fly.Can we call out the below change (in the -1550,7 +1525,8 code chunk) in the commit message, or split it out to different patch
* Adding the if check in
amd_pstate_epp_update_limit()
Yeah will add to commit meesage.
Quoted 5 lines
Quoted 3 lines
Signed-off-by Mario Limonciello <[email protected]>--
We need one more hyphen here I think i.e."---", otherwise the version info is showing up in the commit message
Ack
Quoted 96 lines
Quoted 96 lines
v3:
* Fix calc error formin_freq
v2:
* Keep cached limits--- drivers/cpufreq/amd-pstate-ut.c | 14 +++---- drivers/cpufreq/amd-pstate.c | 70 +++++++++++---------------------- drivers/cpufreq/amd-pstate.h | 9 +---- 3 files changed, 32 insertions(+), 61 deletions(-)drivers/cpufreq/amd-pstate-ut.c +7
-7@@ -214,14 +214,14 @@ static void amd_pstate_ut_check_freq(u32 index)break ; cpudata = policy->driver_data; -if (!((cpudata->max_freq >= cpudata->nominal_freq) && +if (!((policy->cpuinfo.max_freq >= cpudata->nominal_freq) && (cpudata->nominal_freq > cpudata->lowest_nonlinear_freq) && - (cpudata->lowest_nonlinear_freq > cpudata->min_freq) && - (cpudata->min_freq >0 ))) { + (cpudata->lowest_nonlinear_freq > policy->cpuinfo.min_freq) && + (policy->cpuinfo.min_freq >0 ))) { amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s cpu%d max=%d >= nominal=%d > lowest_nonlinear=%d > min=%d > 0, the formula is incorrect!\n" , - __func__, cpu, cpudata->max_freq, cpudata->nominal_freq, - cpudata->lowest_nonlinear_freq, cpudata->min_freq); + __func__, cpu, policy->cpuinfo.max_freq, cpudata->nominal_freq, + cpudata->lowest_nonlinear_freq, policy->cpuinfo.min_freq); goto skip_test; }@@ -233,13 +233,13 @@ static void amd_pstate_ut_check_freq(u32 index) }if (cpudata->boost_supported) { -if ((policy->max == cpudata->max_freq) || +if ((policy->max == policy->cpuinfo.max_freq) || (policy->max == cpudata->nominal_freq)) amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_PASS ;else { amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s cpu%d policy_max=%d should be equal cpu_max=%d or cpu_nominal=%d !\n" , - __func__, cpu, policy->max, cpudata->max_freq, + __func__, cpu, policy->max, policy->cpuinfo.max_freq, cpudata->nominal_freq); goto skip_test; }drivers/cpufreq/amd-pstate.c +2
-14@@ -717,7 +717,7 @@ static int amd_pstate_cpu_boost_update(struct cpufreq_policy *policy, bool on)int ret =0 ; nominal_freq =READ_ONCE (cpudata->nominal_freq); - max_freq =READ_ONCE (cpudata->max_freq); + max_freq =perf_to_freq (cpudata,READ_ONCE (cpudata->highest_perf));if (on) policy->cpuinfo.max_freq = max_freq;@@ -901,35 +901,26 @@ static u32 amd_pstate_get_transition_latency(unsigned int cpu)static int amd_pstate_init_freq (struct amd_cpudata *cpudata) {int ret; -u32 min_freq, max_freq; -u32 nominal_freq, lowest_nonlinear_freq; +u32 min_freq, nominal_freq, lowest_nonlinear_freq;struct cppc_perf_caps cppc_perf; ret =cppc_get_perf_caps (cpudata->cpu, &cppc_perf);if (ret)return ret; -if (quirks && quirks->lowest_freq) - min_freq = quirks->lowest_freq; -else - min_freq = cppc_perf.lowest_freq; -if (quirks && quirks->nominal_freq) nominal_freq = quirks->nominal_freq;else nominal_freq = cppc_perf.nominal_freq; - min_freq *=1000 ; nominal_freq *=1000 ; -WRITE_ONCE (cpudata->nominal_freq, nominal_freq); -WRITE_ONCE (cpudata->min_freq, min_freq); - - max_freq =perf_to_freq (cpudata, cpudata->highest_perf); - lowest_nonlinear_freq =perf_to_freq (cpudata, cpudata->lowest_nonlinear_perf);
Quoted 5 lines
drivers/cpufreq/amd-pstate.c static u32 amd_pstate_get_transition_latency(unsigned int cpu) · line 919
Quoted 3 lines
drivers/cpufreq/amd-pstate.c +1
-2-WRITE_ONCE (cpudata->lowest_nonlinear_freq, lowest_nonlinear_freq); -WRITE_ONCE (cpudata->max_freq, max_freq); +if (quirks && quirks->lowest_freq) {We can avoid the "{" for single line if statement, to keep checkpatch happy
This is one of the reason that I don't like to treat checkpatch as gospil. I added it specficially to avoid back and forth for the new patch. In this case I plan to keep it for that reason.
Quoted 8 lines
drivers/cpufreq/amd-pstate.c static u32 amd_pstate_get_transition_latency(unsigned int cpu) · line 923
Quoted 5 lines
drivers/cpufreq/amd-pstate.c +4
-0+ min_freq = quirks->lowest_freq; + }else + min_freq = cppc_perf.lowest_freq; + min_freq *=1000 ;I see that this
min_freqpart of the code is unchanged, just moved few lines below. If the moving is unintended can we avoid it, so that the diff is optimal.
Sure I'll see if I can re-order it a bit to keep it the same.
Quoted 11 lines
drivers/cpufreq/amd-pstate.c static int amd_pstate_init_freq(struct amd_cpudata *cpudata) · line 940
Quoted 9 lines
drivers/cpufreq/amd-pstate.c +0
-1/** * Below values need to be initialized correctly, otherwise driver will fail to load @@ -937,12 +928,15 @@ static int amd_pstate_init_freq(struct amd_cpudata *cpudata)* lowest_nonlinear_freq is a value between [min_freq, nominal_freq] * Check _CPC in ACPI table objects if any values are incorrect */ -if (min_freq <=0 || max_freq <=0 || nominal_freq <=0 || min_freq > max_freq) {Shouldn't we retain these sanity checks for
min_freqandmax_freq?
Now that we're using the helpers isn't it impossible to end up with negative values?
Quoted 148 lines
Thanks,
DhananjayQuoted 143 lines
drivers/cpufreq/amd-pstate.c +16
-30-pr_err ("min_freq(%d) or max_freq(%d) or nominal_freq(%d) value is incorrect\n" , - min_freq, max_freq, nominal_freq); +if (nominal_freq <=0 ) { +pr_err ("nominal_freq(%d) value is incorrect\n" , + nominal_freq);return -EINVAL ; } + lowest_nonlinear_freq =perf_to_freq (cpudata, cpudata->lowest_nonlinear_perf); +WRITE_ONCE (cpudata->lowest_nonlinear_freq, lowest_nonlinear_freq); +if (lowest_nonlinear_freq <= min_freq || lowest_nonlinear_freq > nominal_freq) {pr_err ("lowest_nonlinear_freq(%d) value is out of range [min_freq(%d), nominal_freq(%d)]\n" , lowest_nonlinear_freq, min_freq, nominal_freq);@@ -954,9 +948,9 @@ static int amd_pstate_init_freq(struct amd_cpudata *cpudata)static int amd_pstate_cpu_init (struct cpufreq_policy *policy) { -int min_freq, max_freq, ret; -struct device *dev;struct amd_cpudata *cpudata; +struct device *dev; +int ret;/* * Resetting PERF_CTL_MSR will put the CPU in P0 frequency, @@ -987,17 +981,11 @@ static int amd_pstate_cpu_init(struct cpufreq_policy *policy)if (ret) goto free_cpudata1; - min_freq =READ_ONCE (cpudata->min_freq); - max_freq =READ_ONCE (cpudata->max_freq); - policy->cpuinfo.transition_latency =amd_pstate_get_transition_latency (policy->cpu); policy->transition_delay_us =amd_pstate_get_transition_delay_us (policy->cpu); - policy->min = min_freq; - policy->max = max_freq; - - policy->cpuinfo.min_freq = min_freq; - policy->cpuinfo.max_freq = max_freq; + policy->cpuinfo.min_freq = policy->min =perf_to_freq (cpudata, cpudata->lowest_perf); + policy->cpuinfo.max_freq = policy->max =perf_to_freq (cpudata, cpudata->highest_perf); policy->boost_enabled =READ_ONCE (cpudata->boost_supported);@@ -1021,9 +1009,6 @@ static int amd_pstate_cpu_init(struct cpufreq_policy *policy) goto free_cpudata2; } - cpudata->max_limit_freq = max_freq; - cpudata->min_limit_freq = min_freq; - policy->driver_data = cpudata;if (!current_pstate_driver->adjust_perf)@@ -1081,14 +1066,10 @@ static int amd_pstate_cpu_suspend(struct cpufreq_policy *policy)static ssize_t show_amd_pstate_max_freq (struct cpufreq_policy *policy,char *buf) { -int max_freq;struct amd_cpudata *cpudata = policy->driver_data; - max_freq =READ_ONCE (cpudata->max_freq); -if (max_freq <0 ) -return max_freq; -return sysfs_emit (buf,"%u\n" , max_freq); +return sysfs_emit (buf,"%u\n" ,perf_to_freq (cpudata,READ_ONCE (cpudata->highest_perf))); } static ssize_t show_amd_pstate_lowest_nonlinear_freq(struct cpufreq_policy *policy,@@ -1446,10 +1427,10 @@ static bool amd_pstate_acpi_pm_profile_undefined(void)static int amd_pstate_epp_cpu_init (struct cpufreq_policy *policy) { -int min_freq, max_freq, ret;struct amd_cpudata *cpudata;struct device *dev;u64 value; +int ret;/* * Resetting PERF_CTL_MSR will put the CPU in P0 frequency, @@ -1480,19 +1461,13 @@ static int amd_pstate_epp_cpu_init(struct cpufreq_policy *policy)if (ret) goto free_cpudata1; - min_freq =READ_ONCE (cpudata->min_freq); - max_freq =READ_ONCE (cpudata->max_freq); - - policy->cpuinfo.min_freq = min_freq; - policy->cpuinfo.max_freq = max_freq; + policy->cpuinfo.min_freq = policy->min =perf_to_freq (cpudata, cpudata->lowest_perf); + policy->cpuinfo.max_freq = policy->max =perf_to_freq (cpudata, cpudata->highest_perf);/* It will be updated by governor */ policy->cur = policy->cpuinfo.min_freq; policy->driver_data = cpudata; - policy->min = policy->cpuinfo.min_freq; - policy->max = policy->cpuinfo.max_freq; - policy->boost_enabled =READ_ONCE (cpudata->boost_supported);/* @@ -1550,7 +1525,8 @@ static int amd_pstate_epp_update_limit(struct cpufreq_policy *policy)struct amd_cpudata *cpudata = policy->driver_data;u8 epp; -amd_pstate_update_min_max_limit (policy); +if (policy->min != cpudata->min_limit_freq || policy->max != cpudata->max_limit_freq) +amd_pstate_update_min_max_limit (policy);if (cpudata->policy ==CPUFREQ_POLICY_PERFORMANCE ) epp =0 ;drivers/cpufreq/amd-pstate.h +2
-7@@ -46,8 +46,6 @@ struct amd_aperf_mperf {* @max_limit_perf: Cached value of the performance corresponding to policy->max * @min_limit_freq: Cached value of policy->min (in khz) * @max_limit_freq: Cached value of policy->max (in khz) -* @max_freq: the frequency (in khz) that mapped to highest_perf -* @min_freq: the frequency (in khz) that mapped to lowest_perf * @nominal_freq: the frequency (in khz) that mapped to nominal_perf * @lowest_nonlinear_freq: the frequency (in khz) that mapped to lowest_nonlinear_perf * @cur: Difference of Aperf/Mperf/tsc count between last and current sample @@ -77,11 +75,8 @@ struct amd_cpudata {u8 prefcore_ranking;u8 min_limit_perf;u8 max_limit_perf; -u32 min_limit_freq; -u32 max_limit_freq; - -u32 max_freq; -u32 min_freq; +u32 min_limit_freq; +u32 max_limit_freq;u32 nominal_freq;u32 lowest_nonlinear_freq;
PATCH v3 4/18 cpufreq/amd-pstate: Move perf values into a union
In reply to Mario LimoncielloFrom: Mario Limonciello <[email protected]>
By storing perf values in a union all the writes and reads can be done atomically, removing the need for some concurrency protections.
While making this change, also drop the cached frequency values, using inline helpers to calculate them on demand from perf value.
---
v3:
* Pick up tag
v2:
* cache perf variable in unit tests
* Drop unnecessary check from amd_pstate_update_min_max_limit()
* Consistency with READ_ONCE()
* Drop unneeded policy checks
* add kdoc
--- drivers/cpufreq/amd-pstate-ut.c | 18 +-- drivers/cpufreq/amd-pstate.c | 195 ++++++++++++++++++-------------- drivers/cpufreq/amd-pstate.h | 49 +++++--- 3 files changed, 151 insertions(+), 111 deletions(-)
drivers/cpufreq/amd-pstate-ut.c +10 -8
@@ -129,6 +129,7 @@ static void amd_pstate_ut_check_perf(u32 index)struct cppc_perf_caps cppc_perf;struct cpufreq_policy *policy =NULL ;struct amd_cpudata *cpudata =NULL ; +union perf_cached cur_perf;for_each_possible_cpu (cpu) { policy =cpufreq_cpu_get (cpu);
@@ -162,19 +163,20 @@ static void amd_pstate_ut_check_perf(u32 index) lowest_perf =AMD_CPPC_LOWEST_PERF (cap1); } -if (highest_perf !=READ_ONCE (cpudata->highest_perf) && !cpudata->hw_prefcore) { + cur_perf =READ_ONCE (cpudata->perf); +if (highest_perf != cur_perf.highest_perf && !cpudata->hw_prefcore) {pr_err ("%s cpu%d highest=%d %d highest perf doesn't match\n" , - __func__, cpu, highest_perf, cpudata->highest_perf); + __func__, cpu, highest_perf, cpudata->perf.highest_perf); goto skip_test; } -if ((nominal_perf !=READ_ONCE (cpudata->nominal_perf)) || - (lowest_nonlinear_perf !=READ_ONCE (cpudata->lowest_nonlinear_perf)) || - (lowest_perf !=READ_ONCE (cpudata->lowest_perf))) { +if (nominal_perf != cur_perf.nominal_perf || + (lowest_nonlinear_perf != cur_perf.lowest_nonlinear_perf) || + (lowest_perf != cur_perf.lowest_perf)) { amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s cpu%d nominal=%d %d lowest_nonlinear=%d %d lowest=%d %d, they should be equal!\n" , - __func__, cpu, nominal_perf, cpudata->nominal_perf, - lowest_nonlinear_perf, cpudata->lowest_nonlinear_perf, - lowest_perf, cpudata->lowest_perf); + __func__, cpu, nominal_perf, cpudata->perf.nominal_perf, + lowest_nonlinear_perf, cpudata->perf.lowest_nonlinear_perf, + lowest_perf, cpudata->perf.lowest_perf); goto skip_test; }
drivers/cpufreq/amd-pstate.c +110 -85
444 lines not on this page · raw message
drivers/cpufreq/amd-pstate.h +31 -18
70 lines not on this page · raw message
Signature · 1 line
2.43.0
Re: [PATCH v3 04/18] cpufreq/amd-pstate: Move perf values into a union
Quoted 38 lines · Mario Limonciello
From: Mario Limonciello <[email protected]>
By storing perf values in a union all the writes and reads can be done atomically, removing the need for some concurrency protections.
While making this change, also drop the cached frequency values, using inline helpers to calculate them on demand from perf value.
Reviewed-by Gautham R. Shenoy <[email protected]>Signed-off-by Mario Limonciello <[email protected]>---
v3:
* Pick up tag
v2:
* cache perf variable in unit tests
* Drop unnecessary check fromamd_pstate_update_min_max_limit()
* Consistency withREAD_ONCE()
* Drop unneeded policy checks
* add kdoc--- drivers/cpufreq/amd-pstate-ut.c | 18 +-- drivers/cpufreq/amd-pstate.c | 195 ++++++++++++++++++-------------- drivers/cpufreq/amd-pstate.h | 49 +++++--- 3 files changed, 151 insertions(+), 111 deletions(-)drivers/cpufreq/amd-pstate-ut.c +1
-0@@ -129,6 +129,7 @@ static void amd_pstate_ut_check_perf(u32 index)struct cppc_perf_caps cppc_perf;struct cpufreq_policy *policy =NULL ;struct amd_cpudata *cpudata =NULL ; +union perf_cached cur_perf;for_each_possible_cpu (cpu) { policy =cpufreq_cpu_get (cpu);
drivers/cpufreq/amd-pstate-ut.c static void amd_pstate_ut_check_perf(u32 index) · line 169
Quoted 9 lines
drivers/cpufreq/amd-pstate-ut.c +3
-2@@ -162,19 +163,20 @@ static void amd_pstate_ut_check_perf(u32 index) lowest_perf =AMD_CPPC_LOWEST_PERF (cap1); } -if (highest_perf !=READ_ONCE (cpudata->highest_perf) && !cpudata->hw_prefcore) { + cur_perf =READ_ONCE (cpudata->perf); +if (highest_perf != cur_perf.highest_perf && !cpudata->hw_prefcore) {pr_err ("%s cpu%d highest=%d %d highest perf doesn't match\n" , - __func__, cpu, highest_perf, cpudata->highest_perf); + __func__, cpu, highest_perf, cpudata->perf.highest_perf);
Can we use cur_perf.highest_perf here ?
Quoted 6 lines
drivers/cpufreq/amd-pstate-ut.c +1
-3goto skip_test; } -if ((nominal_perf !=READ_ONCE (cpudata->nominal_perf)) || - (lowest_nonlinear_perf !=READ_ONCE (cpudata->lowest_nonlinear_perf)) || - (lowest_perf !=READ_ONCE (cpudata->lowest_perf))) { + if (nominal_perf != cur_perf.nominal_perf ||
drivers/cpufreq/amd-pstate-ut.c static void amd_pstate_ut_check_perf(u32 index) · line 179
Quoted 10 lines
drivers/cpufreq/amd-pstate-ut.c +5
-3+ (lowest_nonlinear_perf != cur_perf.lowest_nonlinear_perf) || + (lowest_perf != cur_perf.lowest_perf)) { amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s cpu%d nominal=%d %d lowest_nonlinear=%d %d lowest=%d %d, they should be equal!\n" , - __func__, cpu, nominal_perf, cpudata->nominal_perf, - lowest_nonlinear_perf, cpudata->lowest_nonlinear_perf, - lowest_perf, cpudata->lowest_perf); + __func__, cpu, nominal_perf, cpudata->perf.nominal_perf, + lowest_nonlinear_perf, cpudata->perf.lowest_nonlinear_perf, + lowest_perf, cpudata->perf.lowest_perf);
Can we use cur_perf.(nominal/lowest_nonlinear/lowest)_perf here as well ?
Quoted 3 lines
drivers/cpufreq/amd-pstate-ut.c +0
-0goto skip_test; }
[Snip]
Quoted 34 lines
drivers/cpufreq/amd-pstate-ut.c +7
-8@@ -888,25 +896,24 @@ static u32 amd_pstate_get_transition_latency(unsigned int cpu) }/* -* amd_pstate_init_freq: Initialize the max_freq, min_freq, -* nominal_freq and lowest_nonlinear_freq for -* the @cpudata object. +* amd_pstate_init_freq: Initialize the nominal_freq and lowest_nonlinear_freq +* for the @cpudata object. * -* Requires: highest_perf, lowest_perf, nominal_perf and -* lowest_nonlinear_perf members of @cpudata to be -* initialized. +* Requires: all perf members of @cpudata to be initialized. * -* Returns 0 on success, non-zero value on failure. +* Returns 0 on success, non-zero value on failure. */ static int amd_pstate_init_freq (struct amd_cpudata *cpudata) { -int ret;u32 min_freq, nominal_freq, lowest_nonlinear_freq;struct cppc_perf_caps cppc_perf; +union perf_cached perf; +int ret; ret =cppc_get_perf_caps (cpudata->cpu, &cppc_perf);if (ret)return ret; + perf =READ_ONCE (cpudata->perf);if (quirks && quirks->nominal_freq) nominal_freq = quirks->nominal_freq;
drivers/cpufreq/amd-pstate-ut.c static int amd_pstate_init_freq(struct amd_cpudata *cpudata) · line 928
Quoted 4 lines
drivers/cpufreq/amd-pstate-ut.c +1
-0@@ -918,6 +925,7 @@ static int amd_pstate_init_freq(struct amd_cpudata *cpudata)if (quirks && quirks->lowest_freq) { min_freq = quirks->lowest_freq; + perf.lowest_perf =freq_to_perf (perf, nominal_freq, min_freq);
I think we forgot to write back this value to the cpudata->perf variable
Quoted 12 lines
drivers/cpufreq/amd-pstate-ut.c +1
-1}else min_freq = cppc_perf.lowest_freq; min_freq *=1000 ;@@ -934,7 +942,7 @@ static int amd_pstate_init_freq(struct amd_cpudata *cpudata)return -EINVAL ; } - lowest_nonlinear_freq =perf_to_freq (cpudata, cpudata->lowest_nonlinear_perf); + lowest_nonlinear_freq =perf_to_freq (perf, nominal_freq, perf.lowest_nonlinear_perf);WRITE_ONCE (cpudata->lowest_nonlinear_freq, lowest_nonlinear_freq);if (lowest_nonlinear_freq <= min_freq || lowest_nonlinear_freq > nominal_freq) {
[Snip]
Quoted 5 lines
drivers/cpufreq/amd-pstate.h +0
-0
drivers/cpufreq/amd-pstate.h line 22
Quoted 10 lines
drivers/cpufreq/amd-pstate.h +7
-0@@ -13,6 +13,34 @@/********************************************************************* * AMD P-state INTERFACE * *********************************************************************/ + +/** +* union perf_cached - A union to cache performance-related data. +* @highest_perf: the maximum performance an individual processor may reach, +* assuming ideal conditions +* For platforms that do not support the preferred core feature, the +* highest_pef may be configured with 166 or 255, to avoid max frequency
s/highest_pef/highest_perf/
Also I think this statement is bit confusing, how about,
"For platforms that support the preferred core feature, the highest_perf value maybe configured to any value in the range 166-256 by the firmware (because the preferred core ranking is encoded in the highest_perf value). To maintain consistency across all platforms, we split the highest_perf and preferred core ranking values into cpudata->perf.highest_perf and cpudata->prefcore_ranking."
Quoted 7 lines
drivers/cpufreq/amd-pstate.h +7
-0+* calculated wrongly. we take the fixed value as the highest_perf. +* @nominal_perf: the maximum sustained performance level of the processor, +* assuming ideal operating conditions +* @lowest_nonlinear_perf: the lowest performance level at which nonlinear power +* savings are achieved +* @lowest_perf: the absolute lowest performance level of the processor +* @min_limit_perf: Cached value of the performance corresponding to policy->min
drivers/cpufreq/amd-pstate.h line 39
Quoted 10 lines
drivers/cpufreq/amd-pstate.h +10
-0+* @max_limit_perf: Cached value of the performance corresponding to policy->max +*/ +union perf_cached { +struct { +u8 highest_perf; +u8 nominal_perf; +u8 lowest_nonlinear_perf; +u8 lowest_perf; +u8 min_limit_perf; +u8 max_limit_perf;
Just a thought, how about adding the "u8 desired_perf" (last requested) and "u8 prefcore_ranking" in this. We can pursue it as a separate patch if you want.
I think there is value in adding desired_perf atleast, so that when we are caching the min, max limits in the perf_cached variable, desired perf level is also atomically updated into the shared cpudata structure.
Thanks,
Dhananjay
Quoted 45 lines
drivers/cpufreq/amd-pstate.h +7
-18+ }; +u64 val; +}; +/** * struct amd_aperf_mperf * @aperf: actual performance frequency clock count @@ -30,20 +58,9 @@ struct amd_aperf_mperf {* @cpu: CPU number * @req: constraint request to apply * @cppc_req_cached: cached performance request hints -* @highest_perf: the maximum performance an individual processor may reach, -* assuming ideal conditions -* For platforms that do not support the preferred core feature, the -* highest_pef may be configured with 166 or 255, to avoid max frequency -* calculated wrongly. we take the fixed value as the highest_perf. -* @nominal_perf: the maximum sustained performance level of the processor, -* assuming ideal operating conditions -* @lowest_nonlinear_perf: the lowest performance level at which nonlinear power -* savings are achieved -* @lowest_perf: the absolute lowest performance level of the processor +* @perf: cached performance-related data * @prefcore_ranking: the preferred core ranking, the higher value indicates a higher * priority. -* @min_limit_perf: Cached value of the performance corresponding to policy->min -* @max_limit_perf: Cached value of the performance corresponding to policy->max * @min_limit_freq: Cached value of policy->min (in khz) * @max_limit_freq: Cached value of policy->max (in khz) * @nominal_freq: the frequency (in khz) that mapped to nominal_perf @@ -68,13 +85,9 @@ struct amd_cpudata {struct freq_qos_request req[2 ];u64 cppc_req_cached; -u8 highest_perf; -u8 nominal_perf; -u8 lowest_nonlinear_perf; -u8 lowest_perf; +union perf_cached perf; +u8 prefcore_ranking; -u8 min_limit_perf; -u8 max_limit_perf;u32 min_limit_freq;u32 max_limit_freq;u32 nominal_freq;
Re: [PATCH v3 04/18] cpufreq/amd-pstate: Move perf values into a union
Quoted 42 lines · Dhananjay Ugwekar
Quoted 41 lines · Mario Limonciello
From: Mario Limonciello <[email protected]>
By storing perf values in a union all the writes and reads can be done atomically, removing the need for some concurrency protections.
While making this change, also drop the cached frequency values, using inline helpers to calculate them on demand from perf value.
Reviewed-by Gautham R. Shenoy <[email protected]>Signed-off-by Mario Limonciello <[email protected]>---
v3:
* Pick up tag
v2:
* cache perf variable in unit tests
* Drop unnecessary check fromamd_pstate_update_min_max_limit()
* Consistency withREAD_ONCE()
* Drop unneeded policy checks
* add kdoc--- drivers/cpufreq/amd-pstate-ut.c | 18 +-- drivers/cpufreq/amd-pstate.c | 195 ++++++++++++++++++-------------- drivers/cpufreq/amd-pstate.h | 49 +++++--- 3 files changed, 151 insertions(+), 111 deletions(-)drivers/cpufreq/amd-pstate-ut.c +1
-0@@ -129,6 +129,7 @@ static void amd_pstate_ut_check_perf(u32 index)struct cppc_perf_caps cppc_perf;struct cpufreq_policy *policy =NULL ;struct amd_cpudata *cpudata =NULL ; +union perf_cached cur_perf;for_each_possible_cpu (cpu) { policy =cpufreq_cpu_get (cpu);@@ -162,19 +163,20 @@ static void amd_pstate_ut_check_perf(u32 index) lowest_perf =AMD_CPPC_LOWEST_PERF (cap1); }
Quoted 7 lines
drivers/cpufreq/amd-pstate-ut.c static void amd_pstate_ut_check_perf(u32 index) · line 169
Quoted 6 lines
drivers/cpufreq/amd-pstate-ut.c +3
-2-if (highest_perf !=READ_ONCE (cpudata->highest_perf) && !cpudata->hw_prefcore) { + cur_perf =READ_ONCE (cpudata->perf); +if (highest_perf != cur_perf.highest_perf && !cpudata->hw_prefcore) {pr_err ("%s cpu%d highest=%d %d highest perf doesn't match\n" , - __func__, cpu, highest_perf, cpudata->highest_perf); + __func__, cpu, highest_perf, cpudata->perf.highest_perf);Can we use cur_perf.highest_perf here ?
Ack.
Quoted 10 lines
Quoted 10 lines
drivers/cpufreq/amd-pstate-ut.c +3
-3goto skip_test; } -if ((nominal_perf !=READ_ONCE (cpudata->nominal_perf)) || - (lowest_nonlinear_perf !=READ_ONCE (cpudata->lowest_nonlinear_perf)) || - (lowest_perf !=READ_ONCE (cpudata->lowest_perf))) { +if (nominal_perf != cur_perf.nominal_perf || + (lowest_nonlinear_perf != cur_perf.lowest_nonlinear_perf) || + (lowest_perf != cur_perf.lowest_perf)) { amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;
Quoted 8 lines
drivers/cpufreq/amd-pstate-ut.c static void amd_pstate_ut_check_perf(u32 index) · line 179
Quoted 7 lines
drivers/cpufreq/amd-pstate-ut.c +3
-3pr_err ("%s cpu%d nominal=%d %d lowest_nonlinear=%d %d lowest=%d %d, they should be equal!\n" , - __func__, cpu, nominal_perf, cpudata->nominal_perf, - lowest_nonlinear_perf, cpudata->lowest_nonlinear_perf, - lowest_perf, cpudata->lowest_perf); + __func__, cpu, nominal_perf, cpudata->perf.nominal_perf, + lowest_nonlinear_perf, cpudata->perf.lowest_nonlinear_perf, + lowest_perf, cpudata->perf.lowest_perf);Can we use cur_perf.(nominal/lowest_nonlinear/lowest)_perf here as well ?
Ack.
Quoted 40 lines
Quoted 4 lines
drivers/cpufreq/amd-pstate-ut.c +0
-0goto skip_test; }[Snip]
Quoted 35 lines
drivers/cpufreq/amd-pstate-ut.c +7
-8@@ -888,25 +896,24 @@ static u32 amd_pstate_get_transition_latency(unsigned int cpu) }/* -* amd_pstate_init_freq: Initialize the max_freq, min_freq, -* nominal_freq and lowest_nonlinear_freq for -* the @cpudata object. +* amd_pstate_init_freq: Initialize the nominal_freq and lowest_nonlinear_freq +* for the @cpudata object. * -* Requires: highest_perf, lowest_perf, nominal_perf and -* lowest_nonlinear_perf members of @cpudata to be -* initialized. +* Requires: all perf members of @cpudata to be initialized. * -* Returns 0 on success, non-zero value on failure. +* Returns 0 on success, non-zero value on failure. */ static int amd_pstate_init_freq (struct amd_cpudata *cpudata) { -int ret;u32 min_freq, nominal_freq, lowest_nonlinear_freq;struct cppc_perf_caps cppc_perf; +union perf_cached perf; +int ret; ret =cppc_get_perf_caps (cpudata->cpu, &cppc_perf);if (ret)return ret; + perf =READ_ONCE (cpudata->perf);if (quirks && quirks->nominal_freq) nominal_freq = quirks->nominal_freq;@@ -918,6 +925,7 @@ static int amd_pstate_init_freq(struct amd_cpudata *cpudata)
Quoted 5 lines
drivers/cpufreq/amd-pstate-ut.c static int amd_pstate_init_freq(struct amd_cpudata *cpudata) · line 928
Quoted 3 lines
drivers/cpufreq/amd-pstate-ut.c +1
-0if (quirks && quirks->lowest_freq) { min_freq = quirks->lowest_freq; + perf.lowest_perf =freq_to_perf (perf, nominal_freq, min_freq);I think we forgot to write back this value to the
cpudata->perfvariable
Ack, great catch.
Quoted 32 lines
Quoted 13 lines
drivers/cpufreq/amd-pstate-ut.c +1
-1}else min_freq = cppc_perf.lowest_freq; min_freq *=1000 ;@@ -934,7 +942,7 @@ static int amd_pstate_init_freq(struct amd_cpudata *cpudata)return -EINVAL ; } - lowest_nonlinear_freq =perf_to_freq (cpudata, cpudata->lowest_nonlinear_perf); + lowest_nonlinear_freq =perf_to_freq (perf, nominal_freq, perf.lowest_nonlinear_perf);WRITE_ONCE (cpudata->lowest_nonlinear_freq, lowest_nonlinear_freq);if (lowest_nonlinear_freq <= min_freq || lowest_nonlinear_freq > nominal_freq) {[Snip]
Quoted 5 lines
drivers/cpufreq/amd-pstate.h +0
-0drivers/cpufreq/amd-pstate.h line 22
Quoted 10 lines
drivers/cpufreq/amd-pstate.h +7
-0@@ -13,6 +13,34 @@/********************************************************************* * AMD P-state INTERFACE * *********************************************************************/ + +/** +* union perf_cached - A union to cache performance-related data. +* @highest_perf: the maximum performance an individual processor may reach, +* assuming ideal conditions +* For platforms that do not support the preferred core feature, the +* highest_pef may be configured with 166 or 255, to avoid max frequency s/highest_pef/highest_perf/
Quoted 7 lines
Also I think this statement is bit confusing, how about,
"For platforms that support the preferred core feature, the
highest_perfvalue maybe configured to any value in the range 166-256 by the firmware (because the preferred core ranking is encoded in thehighest_perfvalue). To maintain consistency across all platforms, we split thehighest_perfand preferred core ranking values intocpudata->perf.highest_perfandcpudata->prefcore_ranking."
I like it, thanks.
Quoted 22 lines
Quoted 8 lines
drivers/cpufreq/amd-pstate.h +7
-0+* calculated wrongly. we take the fixed value as the highest_perf. +* @nominal_perf: the maximum sustained performance level of the processor, +* assuming ideal operating conditions +* @lowest_nonlinear_perf: the lowest performance level at which nonlinear power +* savings are achieved +* @lowest_perf: the absolute lowest performance level of the processor +* @min_limit_perf: Cached value of the performance corresponding to policy->min drivers/cpufreq/amd-pstate.h line 39
Quoted 10 lines
drivers/cpufreq/amd-pstate.h +10
-0+* @max_limit_perf: Cached value of the performance corresponding to policy->max +*/ +union perf_cached { +struct { +u8 highest_perf; +u8 nominal_perf; +u8 lowest_nonlinear_perf; +u8 lowest_perf; +u8 min_limit_perf; +u8 max_limit_perf;Just a thought, how about adding the "u8
desired_perf" (last requested) and "u8prefcore_ranking" in this. We can pursue it as a separate patch if you want.
Quoted 3 lines
I think there is value in adding
desired_perfatleast, so that when we are caching the min, max limits in theperf_cachedvariable, desired perf level is also atomically updated into the shared cpudata structure.
Can you see if there is any performance advantage to caching these? If there is, can you please do a follow up to my v5 series?
It's going to mean another write in amd_pstate_update() potentially.
Quoted 50 lines
Thanks,
DhananjayQuoted 45 lines
drivers/cpufreq/amd-pstate.h +7
-18+ }; +u64 val; +}; +/** * struct amd_aperf_mperf * @aperf: actual performance frequency clock count @@ -30,20 +58,9 @@ struct amd_aperf_mperf {* @cpu: CPU number * @req: constraint request to apply * @cppc_req_cached: cached performance request hints -* @highest_perf: the maximum performance an individual processor may reach, -* assuming ideal conditions -* For platforms that do not support the preferred core feature, the -* highest_pef may be configured with 166 or 255, to avoid max frequency -* calculated wrongly. we take the fixed value as the highest_perf. -* @nominal_perf: the maximum sustained performance level of the processor, -* assuming ideal operating conditions -* @lowest_nonlinear_perf: the lowest performance level at which nonlinear power -* savings are achieved -* @lowest_perf: the absolute lowest performance level of the processor +* @perf: cached performance-related data * @prefcore_ranking: the preferred core ranking, the higher value indicates a higher * priority. -* @min_limit_perf: Cached value of the performance corresponding to policy->min -* @max_limit_perf: Cached value of the performance corresponding to policy->max * @min_limit_freq: Cached value of policy->min (in khz) * @max_limit_freq: Cached value of policy->max (in khz) * @nominal_freq: the frequency (in khz) that mapped to nominal_perf @@ -68,13 +85,9 @@ struct amd_cpudata {struct freq_qos_request req[2 ];u64 cppc_req_cached; -u8 highest_perf; -u8 nominal_perf; -u8 lowest_nonlinear_perf; -u8 lowest_perf; +union perf_cached perf; +u8 prefcore_ranking; -u8 min_limit_perf; -u8 max_limit_perf;u32 min_limit_freq;u32 max_limit_freq;u32 nominal_freq;
Re: [PATCH v3 04/18] cpufreq/amd-pstate: Move perf values into a union
Quoted 27 lines · Mario Limonciello
Quoted 26 lines · Dhananjay Ugwekar
Quoted 25 lines · Mario Limonciello
From: Mario Limonciello <[email protected]>
By storing perf values in a union all the writes and reads can be done atomically, removing the need for some concurrency protections.
While making this change, also drop the cached frequency values, using inline helpers to calculate them on demand from perf value.
Reviewed-by Gautham R. Shenoy <[email protected]>Signed-off-by Mario Limonciello <[email protected]>---
v3:
* Pick up tag
v2:
* cache perf variable in unit tests
* Drop unnecessary check fromamd_pstate_update_min_max_limit()
* Consistency withREAD_ONCE()
* Drop unneeded policy checks
* add kdoc
---
drivers/cpufreq/amd-pstate-ut.c| 18 +-- drivers/cpufreq/amd-pstate.c | 195 ++++++++++++++++++-------------- drivers/cpufreq/amd-pstate.h | 49 +++++---3 files changed, 151 insertions(+), 111 deletions(-)
[Snip]
Quoted 21 lines
Quoted 21 lines
Quoted 9 lines
+ * calculated wrongly. we take the fixed value as the
highest_perf.
+ * @nominal_perf: the maximum sustained performance level of the processor,
+ * assuming ideal operating conditions
+ * @lowest_nonlinear_perf: the lowest performance level at which nonlinear power
+ * savings are achieved
+ * @lowest_perf: the absolute lowest performance level of the processor
+ * @min_limit_perf: Cached value of the performance corresponding topolicy->min
+ * @max_limit_perf: Cached value of the performance corresponding topolicy->max
+ */Quoted 8 lines
+union
perf_cached{
+ struct {
+ u8highest_perf;
+ u8nominal_perf;
+ u8lowest_nonlinear_perf;
+ u8lowest_perf;
+ u8min_limit_perf;
+ u8max_limit_perf;Just a thought, how about adding the "u8
desired_perf" (last requested) and "u8prefcore_ranking" in this. We can pursue it as a separate patch if you want.
Quoted 6 lines
Quoted 3 lines
I think there is value in adding
desired_perfatleast, so that when we are caching the min, max limits in theperf_cachedvariable, desired perf level is also atomically updated into the shared cpudata structure.Can you see if there is any performance advantage to caching these? If there is, can you please do a follow up to my v5 series?
There might not be a performance advantage, but I thought it will tie up the entire perf updation (min, max, des) into one atomic write to perf_cached. But the min, max and des_perf updation is divided into different functions currently. So it may not work as I'm imagining.
Quoted 2 lines
It's going to mean another write in
amd_pstate_update()potentially.
Yea, right, I'll investigate and see if it is worth doing.
Quoted 4 lines
Quoted 4 lines
Thanks,
Dhananjay
PATCH v3 5/18 cpufreq/amd-pstate: Overhaul locking
In reply to Mario LimoncielloFrom: Mario Limonciello <[email protected]>
amd_pstate_cpu_boost_update() and refresh_frequency_limits() both update the policy state and have nothing to do with the amd-pstate driver itself.
A global "limits" lock doesn't make sense because each CPU can have policies changed independently. Each time a CPU changes values they will atomically be written to the per-CPU perf member. Drop per CPU locking cases.
The remaining "global" driver lock is used to ensure that only one entity can change driver modes at a given time.
--- drivers/cpufreq/amd-pstate.c | 13 +++---------- 1 file changed, 3 insertions(+), 10 deletions(-)
drivers/cpufreq/amd-pstate.c +3 -10
@@ -196,7 +196,6 @@ static inline int get_mode_idx_from_str(const char *str, size_t size)return -EINVAL ; } -static DEFINE_MUTEX (amd_pstate_limits_lock);static DEFINE_MUTEX (amd_pstate_driver_lock);static u8 msr_get_epp (struct amd_cpudata *cpudata)
@@ -752,7 +751,6 @@ static int amd_pstate_set_boost(struct cpufreq_policy *policy, int state)pr_err ("Boost mode is not supported by this processor or SBIOS\n" );return -EOPNOTSUPP ; } -guard (mutex)(&amd_pstate_driver_lock); ret =amd_pstate_cpu_boost_update (policy, state);refresh_frequency_limits (policy);
@@ -1173,8 +1171,6 @@ static ssize_t store_energy_performance_preference(if (ret <0 )return -EINVAL ; -guard (mutex)(&amd_pstate_limits_lock); - ret =amd_pstate_set_energy_pref_index (policy, ret);return ret ? ret : count;
@@ -1347,8 +1343,10 @@ int amd_pstate_update_status(const char *buf, size_t size)if (mode_idx <0 || mode_idx >=AMD_PSTATE_MAX )return -EINVAL ; -if (mode_state_machine[cppc_state][mode_idx]) +if (mode_state_machine[cppc_state][mode_idx]) { +guard (mutex)(&amd_pstate_driver_lock);return mode_state_machine[cppc_state][mode_idx](mode_idx); + }return 0 ; }
@@ -1369,7 +1367,6 @@ static ssize_t status_store(struct device *a, struct device_attribute *b,char *p =memchr (buf,'\n' , count);int ret; -guard (mutex)(&amd_pstate_driver_lock); ret =amd_pstate_update_status (buf, p ? p - buf : count);return ret <0 ? ret : count;
@@ -1641,8 +1638,6 @@ static int amd_pstate_epp_cpu_offline(struct cpufreq_policy *policy)if (cpudata->suspended)return 0 ; -guard (mutex)(&amd_pstate_limits_lock); -if (trace_amd_pstate_epp_perf_enabled ()) { trace_amd_pstate_epp_perf(cpudata->cpu, perf.highest_perf, AMD_CPPC_EPP_BALANCE_POWERSAVE,
@@ -1682,8 +1677,6 @@ static int amd_pstate_epp_resume(struct cpufreq_policy *policy)struct amd_cpudata *cpudata = policy->driver_data;if (cpudata->suspended) { -guard (mutex)(&amd_pstate_limits_lock); -/* enable amd pstate from suspend state*/ amd_pstate_epp_reenable (policy);
Signature · 1 line
2.43.0
PATCH v3 6/18 cpufreq/amd-pstate: Drop `cppc_cap1_cached`
In reply to Mario LimoncielloFrom: Mario Limonciello <[email protected]>
The cppc_cap1_cached variable isn't used at all, there is no need to read it at initialization for each CPU.
--- drivers/cpufreq/amd-pstate.c | 5 ----- drivers/cpufreq/amd-pstate.h | 2 -- 2 files changed, 7 deletions(-)
drivers/cpufreq/amd-pstate.c +0 -5
@@ -1511,11 +1511,6 @@ static int amd_pstate_epp_cpu_init(struct cpufreq_policy *policy)if (ret)return ret;WRITE_ONCE (cpudata->cppc_req_cached, value); - - ret =rdmsrl_on_cpu (cpudata->cpu,MSR_AMD_CPPC_CAP1 , &value); -if (ret) -return ret; -WRITE_ONCE (cpudata->cppc_cap1_cached, value); } ret =amd_pstate_set_epp (cpudata, cpudata->epp_default);if (ret)
drivers/cpufreq/amd-pstate.h +0 -2
@@ -74,7 +74,6 @@ struct amd_aperf_mperf {* AMD P-State driver supports preferred core featue. * @epp_cached: Cached CPPC energy-performance preference value * @policy: Cpufreq policy value -* @cppc_cap1_cached Cached MSR_AMD_CPPC_CAP1 register value * * The amd_cpudata is key private data for each CPU thread in AMD P-State, and * represents all the attributes and goals that AMD P-State requests at runtime.
@@ -103,7 +102,6 @@ struct amd_cpudata {/* EPP feature related attributes*/ u8 epp_cached;u32 policy; -u64 cppc_cap1_cached;bool suspended;u8 epp_default; };
Signature · 1 line
2.43.0
PATCH v3 7/18 cpufreq/amd-pstate-ut: Use _free macro to free put policy
In reply to Mario LimoncielloFrom: Mario Limonciello <[email protected]>
Using a scoped cleanup macro simplifies cleanup code.
--- drivers/cpufreq/amd-pstate-ut.c | 33 ++++++++++++++------------------- 1 file changed, 14 insertions(+), 19 deletions(-)
drivers/cpufreq/amd-pstate-ut.c +14 -19
@@ -26,6 +26,7 @@#include <linux/module.h> #include <linux/moduleparam.h> #include <linux/fs.h> +#include <linux/cleanup.h> #include <acpi/cppc_acpi.h>
@@ -127,11 +128,12 @@ static void amd_pstate_ut_check_perf(u32 index)u32 highest_perf =0 , nominal_perf =0 , lowest_nonlinear_perf =0 , lowest_perf =0 ;u64 cap1 =0 ;struct cppc_perf_caps cppc_perf; -struct cpufreq_policy *policy =NULL ;struct amd_cpudata *cpudata =NULL ;union perf_cached cur_perf;for_each_possible_cpu (cpu) { + struct cpufreq_policy *policy __free(put_cpufreq_policy) = NULL; + policy =cpufreq_cpu_get (cpu);if (!policy)break ;
@@ -142,7 +144,7 @@ static void amd_pstate_ut_check_perf(u32 index)if (ret) { amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s cppc_get_perf_caps ret=%d error!\n" , __func__, ret); - goto skip_test; +return ; } highest_perf = cppc_perf.highest_perf;
@@ -154,7 +156,7 @@ static void amd_pstate_ut_check_perf(u32 index)if (ret) { amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s read CPPC_CAP1 ret=%d error!\n" , __func__, ret); - goto skip_test; +return ; } highest_perf =AMD_CPPC_HIGHEST_PERF (cap1);
@@ -167,7 +169,7 @@ static void amd_pstate_ut_check_perf(u32 index)if (highest_perf != cur_perf.highest_perf && !cpudata->hw_prefcore) {pr_err ("%s cpu%d highest=%d %d highest perf doesn't match\n" , __func__, cpu, highest_perf, cpudata->perf.highest_perf); - goto skip_test; +return ; } if (nominal_perf != cur_perf.nominal_perf || (lowest_nonlinear_perf != cur_perf.lowest_nonlinear_perf) ||
@@ -177,7 +179,7 @@ static void amd_pstate_ut_check_perf(u32 index) __func__, cpu, nominal_perf, cpudata->perf.nominal_perf, lowest_nonlinear_perf, cpudata->perf.lowest_nonlinear_perf, lowest_perf, cpudata->perf.lowest_perf); - goto skip_test; +return ; } if (!((highest_perf >= nominal_perf) &&
@@ -188,15 +190,11 @@ static void amd_pstate_ut_check_perf(u32 index)pr_err ("%s cpu%d highest=%d >= nominal=%d > lowest_nonlinear=%d > lowest=%d > 0, the formula is incorrect!\n" , __func__, cpu, highest_perf, nominal_perf, lowest_nonlinear_perf, lowest_perf); - goto skip_test; +return ; } -cpufreq_cpu_put (policy); } amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_PASS ; -return ; -skip_test: -cpufreq_cpu_put (policy); }/*
@@ -207,10 +205,11 @@ static void amd_pstate_ut_check_perf(u32 index)static void amd_pstate_ut_check_freq (u32 index) {int cpu =0 ; -struct cpufreq_policy *policy =NULL ;struct amd_cpudata *cpudata =NULL ;for_each_possible_cpu (cpu) { + struct cpufreq_policy *policy __free(put_cpufreq_policy) = NULL; + policy =cpufreq_cpu_get (cpu);if (!policy)break ;
@@ -224,14 +223,14 @@ static void amd_pstate_ut_check_freq(u32 index)pr_err ("%s cpu%d max=%d >= nominal=%d > lowest_nonlinear=%d > min=%d > 0, the formula is incorrect!\n" , __func__, cpu, policy->cpuinfo.max_freq, cpudata->nominal_freq, cpudata->lowest_nonlinear_freq, policy->cpuinfo.min_freq); - goto skip_test; +return ; }if (cpudata->lowest_nonlinear_freq != policy->min) { amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s cpu%d cpudata_lowest_nonlinear_freq=%d policy_min=%d, they should be equal!\n" , __func__, cpu, cpudata->lowest_nonlinear_freq, policy->min); - goto skip_test; +return ; }if (cpudata->boost_supported) {
@@ -243,20 +242,16 @@ static void amd_pstate_ut_check_freq(u32 index)pr_err ("%s cpu%d policy_max=%d should be equal cpu_max=%d or cpu_nominal=%d !\n" , __func__, cpu, policy->max, policy->cpuinfo.max_freq, cpudata->nominal_freq); - goto skip_test; +return ; } }else { amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s cpu%d must support boost!\n" , __func__, cpu); - goto skip_test; +return ; } -cpufreq_cpu_put (policy); } amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_PASS ; -return ; -skip_test: -cpufreq_cpu_put (policy); }static int amd_pstate_set_mode (enum amd_pstate_mode mode)
Signature · 1 line
2.43.0
PATCH v3 8/18 cpufreq/amd-pstate-ut: Allow lowest nonlinear and lowest to be the same
In reply to Mario LimoncielloFrom: Mario Limonciello <[email protected]>
Several Ryzen AI processors support the exact same value for lowest nonlinear perf and lowest perf. Loosen up the unit tests to allow this scenario.
--- drivers/cpufreq/amd-pstate-ut.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/cpufreq/amd-pstate-ut.c +2 -2
@@ -184,7 +184,7 @@ static void amd_pstate_ut_check_perf(u32 index)if (!((highest_perf >= nominal_perf) && (nominal_perf > lowest_nonlinear_perf) && - (lowest_nonlinear_perf > lowest_perf) && + (lowest_nonlinear_perf >= lowest_perf) && (lowest_perf >0 ))) { amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ; pr_err("%s cpu%d highest=%d >= nominal=%d > lowest_nonlinear=%d > lowest=%d > 0, the formula is incorrect!\n",
@@ -217,7 +217,7 @@ static void amd_pstate_ut_check_freq(u32 index)if (!((policy->cpuinfo.max_freq >= cpudata->nominal_freq) && (cpudata->nominal_freq > cpudata->lowest_nonlinear_freq) && - (cpudata->lowest_nonlinear_freq > policy->cpuinfo.min_freq) && + (cpudata->lowest_nonlinear_freq >= policy->cpuinfo.min_freq) && (policy->cpuinfo.min_freq >0 ))) { amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ; pr_err("%s cpu%d max=%d >= nominal=%d > lowest_nonlinear=%d > min=%d > 0, the formula is incorrect!\n",
Signature · 1 line
2.43.0
PATCH v3 9/18 cpufreq/amd-pstate-ut: Drop SUCCESS and FAIL enums
In reply to Mario LimoncielloFrom: Mario Limonciello <[email protected]>
Enums are effectively used as a boolean and don't show the return value of the failing call.
Instead of using enums switch to returning the actual return code from the unit test.
--- drivers/cpufreq/amd-pstate-ut.c | 143 ++++++++++++-------------------- 1 file changed, 55 insertions(+), 88 deletions(-)
drivers/cpufreq/amd-pstate-ut.c +55 -88
@@ -32,30 +32,20 @@#include "amd-pstate.h" -/* -* Abbreviations: -* amd_pstate_ut: used as a shortform for AMD P-State unit test. -* It helps to keep variable names smaller, simpler -*/ -enum amd_pstate_ut_result { -AMD_PSTATE_UT_RESULT_PASS , -AMD_PSTATE_UT_RESULT_FAIL , -};struct amd_pstate_ut_struct {const char *name; -void (*func)(u32 index); -enum amd_pstate_ut_result result; +int (*func)(u32 index); };/* * Kernel module for testing the AMD P-State unit test */ -static void amd_pstate_ut_acpi_cpc_valid (u32 index); -static void amd_pstate_ut_check_enabled (u32 index); -static void amd_pstate_ut_check_perf (u32 index); -static void amd_pstate_ut_check_freq (u32 index); -static void amd_pstate_ut_check_driver (u32 index); +static int amd_pstate_ut_acpi_cpc_valid (u32 index); +static int amd_pstate_ut_check_enabled (u32 index); +static int amd_pstate_ut_check_perf (u32 index); +static int amd_pstate_ut_check_freq (u32 index); +static int amd_pstate_ut_check_driver (u32 index);static struct amd_pstate_ut_struct amd_pstate_ut_cases[] = { {"amd_pstate_ut_acpi_cpc_valid" , amd_pstate_ut_acpi_cpc_valid },
@@ -78,51 +68,46 @@ static bool get_shared_mem(void)/* * check the _CPC object is present in SBIOS. */ -static void amd_pstate_ut_acpi_cpc_valid (u32 index) +static int amd_pstate_ut_acpi_cpc_valid (u32 index) { -if (acpi_cpc_valid ()) - amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_PASS ; -else { - amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ; +if (!acpi_cpc_valid ()) {pr_err ("%s the _CPC object is not present in SBIOS!\n" , __func__); +return -EINVAL ; } + +return 0 ; } -static void amd_pstate_ut_pstate_enable (u32 index) +/* +* check if amd pstate is enabled +*/ +static int amd_pstate_ut_check_enabled (u32 index) { -int ret =0 ;u64 cppc_enable =0 ; +int ret; + +if (get_shared_mem ()) +return 0 ; ret =rdmsrl_safe (MSR_AMD_CPPC_ENABLE , &cppc_enable);if (ret) { - amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s rdmsrl_safe MSR_AMD_CPPC_ENABLE ret=%d error!\n" , __func__, ret); -return ; +return ret; } -if (cppc_enable) - amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_PASS ; -else { - amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ; + +if (!cppc_enable) {pr_err ("%s amd pstate must be enabled!\n" , __func__); +return -EINVAL ; } -} -/* -* check if amd pstate is enabled -*/ -static void amd_pstate_ut_check_enabled (u32 index) -{ -if (get_shared_mem ()) - amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_PASS ; -else -amd_pstate_ut_pstate_enable (index); +return 0 ; }/* * check if performance values are reasonable. * highest_perf >= nominal_perf > lowest_nonlinear_perf > lowest_perf > 0 */ -static void amd_pstate_ut_check_perf (u32 index) +static int amd_pstate_ut_check_perf (u32 index) {int cpu =0 , ret =0 ;u32 highest_perf =0 , nominal_perf =0 , lowest_nonlinear_perf =0 , lowest_perf =0 ;
@@ -142,9 +127,8 @@ static void amd_pstate_ut_check_perf(u32 index)if (get_shared_mem ()) { ret =cppc_get_perf_caps (cpu, &cppc_perf);if (ret) { - amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s cppc_get_perf_caps ret=%d error!\n" , __func__, ret); -return ; +return ret; } highest_perf = cppc_perf.highest_perf;
@@ -154,9 +138,8 @@ static void amd_pstate_ut_check_perf(u32 index) }else { ret =rdmsrl_safe_on_cpu (cpu,MSR_AMD_CPPC_CAP1 , &cap1);if (ret) { - amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s read CPPC_CAP1 ret=%d error!\n" , __func__, ret); -return ; +return ret; } highest_perf =AMD_CPPC_HIGHEST_PERF (cap1);
@@ -169,32 +152,30 @@ static void amd_pstate_ut_check_perf(u32 index)if (highest_perf != cur_perf.highest_perf && !cpudata->hw_prefcore) {pr_err ("%s cpu%d highest=%d %d highest perf doesn't match\n" , __func__, cpu, highest_perf, cpudata->perf.highest_perf); -return ; +return -EINVAL ; }if (nominal_perf != cur_perf.nominal_perf || (lowest_nonlinear_perf != cur_perf.lowest_nonlinear_perf) || (lowest_perf != cur_perf.lowest_perf)) { - amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s cpu%d nominal=%d %d lowest_nonlinear=%d %d lowest=%d %d, they should be equal!\n" , __func__, cpu, nominal_perf, cpudata->perf.nominal_perf, lowest_nonlinear_perf, cpudata->perf.lowest_nonlinear_perf, lowest_perf, cpudata->perf.lowest_perf); -return ; +return -EINVAL ; }if (!((highest_perf >= nominal_perf) && (nominal_perf > lowest_nonlinear_perf) && (lowest_nonlinear_perf >= lowest_perf) && (lowest_perf >0 ))) { - amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s cpu%d highest=%d >= nominal=%d > lowest_nonlinear=%d > lowest=%d > 0, the formula is incorrect!\n" , __func__, cpu, highest_perf, nominal_perf, lowest_nonlinear_perf, lowest_perf); -return ; +return -EINVAL ; } } - amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_PASS ; +return 0 ; }/*
@@ -202,7 +183,7 @@ static void amd_pstate_ut_check_perf(u32 index)* max_freq >= nominal_freq > lowest_nonlinear_freq > min_freq > 0 * check max freq when set support boost mode. */ -static void amd_pstate_ut_check_freq (u32 index) +static int amd_pstate_ut_check_freq (u32 index) {int cpu =0 ;struct amd_cpudata *cpudata =NULL ;
@@ -219,39 +200,33 @@ static void amd_pstate_ut_check_freq(u32 index) (cpudata->nominal_freq > cpudata->lowest_nonlinear_freq) && (cpudata->lowest_nonlinear_freq >= policy->cpuinfo.min_freq) && (policy->cpuinfo.min_freq > 0))) { - amd_pstate_ut_cases[index].result = AMD_PSTATE_UT_RESULT_FAIL;pr_err ("%s cpu%d max=%d >= nominal=%d > lowest_nonlinear=%d > min=%d > 0, the formula is incorrect!\n" , __func__, cpu, policy->cpuinfo.max_freq, cpudata->nominal_freq, cpudata->lowest_nonlinear_freq, policy->cpuinfo.min_freq); -return ; +return -EINVAL ; }if (cpudata->lowest_nonlinear_freq != policy->min) { - amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s cpu%d cpudata_lowest_nonlinear_freq=%d policy_min=%d, they should be equal!\n" , __func__, cpu, cpudata->lowest_nonlinear_freq, policy->min); -return ; +return -EINVAL ; }if (cpudata->boost_supported) { -if ((policy->max == policy->cpuinfo.max_freq) || - (policy->max == cpudata->nominal_freq)) - amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_PASS ; -else { - amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ; +if ((policy->max != policy->cpuinfo.max_freq) && + (policy->max != cpudata->nominal_freq)) {pr_err ("%s cpu%d policy_max=%d should be equal cpu_max=%d or cpu_nominal=%d !\n" , __func__, cpu, policy->max, policy->cpuinfo.max_freq, cpudata->nominal_freq); -return ; +return -EINVAL ; } }else { - amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_FAIL ;pr_err ("%s cpu%d must support boost!\n" , __func__, cpu); -return ; +return -EINVAL ; } } - amd_pstate_ut_cases[index].result =AMD_PSTATE_UT_RESULT_PASS ; +return 0 ; }static int amd_pstate_set_mode (enum amd_pstate_mode mode)
@@ -263,32 +238,28 @@ static int amd_pstate_set_mode(enum amd_pstate_mode mode)return amd_pstate_update_status (mode_str,strlen (mode_str)); } -static void amd_pstate_ut_check_driver (u32 index) +static int amd_pstate_ut_check_driver (u32 index) {enum amd_pstate_mode mode1, mode2 =AMD_PSTATE_DISABLE ; -int ret;for (mode1 =AMD_PSTATE_DISABLE ; mode1 <AMD_PSTATE_MAX ; mode1++) { - ret =amd_pstate_set_mode (mode1); +int ret =amd_pstate_set_mode (mode1);if (ret) - goto out; +return ret;for (mode2 =AMD_PSTATE_DISABLE ; mode2 <AMD_PSTATE_MAX ; mode2++) {if (mode1 == mode2)continue ; ret =amd_pstate_set_mode (mode2); -if (ret) - goto out; +if (ret) { +pr_err ("%s: failed to update status for %s->%s\n" , __func__, +amd_pstate_get_mode_string (mode1), +amd_pstate_get_mode_string (mode2)); +return ret; + } } } -out: -if (ret) -pr_warn ("%s: failed to update status for %s->%s: %d\n" , __func__, -amd_pstate_get_mode_string (mode1), -amd_pstate_get_mode_string (mode2), ret); - - amd_pstate_ut_cases[index].result = ret ? -AMD_PSTATE_UT_RESULT_FAIL : -AMD_PSTATE_UT_RESULT_PASS ; + +return 0 ; }static int __init amd_pstate_ut_init (void )
@@ -296,16 +267,12 @@ static int __init amd_pstate_ut_init(void)u32 i =0 , arr_size =ARRAY_SIZE (amd_pstate_ut_cases);for (i =0 ; i < arr_size; i++) { - amd_pstate_ut_cases[i].func (i); -switch (amd_pstate_ut_cases[i].result) { -case AMD_PSTATE_UT_RESULT_PASS : +int ret = amd_pstate_ut_cases[i].func (i); + +if (ret) +pr_err ("%-4d %-20s\t fail: %d!\n" , i+1 , amd_pstate_ut_cases[i].name, ret); +else pr_info ("%-4d %-20s\t success!\n" , i+1 , amd_pstate_ut_cases[i].name); -break ; -case AMD_PSTATE_UT_RESULT_FAIL : -default : -pr_info ("%-4d %-20s\t fail!\n" , i+1 , amd_pstate_ut_cases[i].name); -break ; - } }return 0 ;
Signature · 1 line
2.43.0
PATCH v3 10/18 cpufreq/amd-pstate-ut: Run on all of the correct CPUs
In reply to Mario LimoncielloFrom: Mario Limonciello <[email protected]>
If a CPU is missing a policy or one has been offlined then the unit test is skipped for the rest of the CPUs on the system.
Instead; iterate online CPUs and skip any missing policies to allow continuing to test the rest of them.
---
v3:
* Only check online CPUs
* Update commit message
--- drivers/cpufreq/amd-pstate-ut.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/cpufreq/amd-pstate-ut.c +4 -4
@@ -116,12 +116,12 @@ static int amd_pstate_ut_check_perf(u32 index)struct amd_cpudata *cpudata =NULL ;union perf_cached cur_perf; -for_each_possible_cpu (cpu) { +for_each_online_cpu (cpu) { struct cpufreq_policy *policy __free(put_cpufreq_policy) = NULL; policy =cpufreq_cpu_get (cpu);if (!policy) -break ; +continue ; cpudata = policy->driver_data;if (get_shared_mem ()) {
@@ -188,12 +188,12 @@ static int amd_pstate_ut_check_freq(u32 index)int cpu =0 ;struct amd_cpudata *cpudata =NULL ; -for_each_possible_cpu (cpu) { +for_each_online_cpu (cpu) { struct cpufreq_policy *policy __free(put_cpufreq_policy) = NULL; policy =cpufreq_cpu_get (cpu);if (!policy) -break ; +continue ; cpudata = policy->driver_data; if (!((policy->cpuinfo.max_freq >= cpudata->nominal_freq) &&
Signature · 1 line
2.43.0
Re: [PATCH v3 10/18] cpufreq/amd-pstate-ut: Run on all of the correct CPUs
Quoted 9 lines · Mario Limonciello
From: Mario Limonciello <[email protected]>
If a CPU is missing a policy or one has been offlined then the unit test is skipped for the rest of the CPUs on the system.
Instead; iterate online CPUs and skip any missing policies to allow continuing to test the rest of them.
Signed-off-by Mario Limonciello <[email protected]>
LGTM
Signature · 2 lines
Thanks and Regards gautham.
Quoted 45 lines
---
v3:
* Only check online CPUs
* Update commit message--- drivers/cpufreq/amd-pstate-ut.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)drivers/cpufreq/amd-pstate-ut.c +4
-4@@ -116,12 +116,12 @@ static int amd_pstate_ut_check_perf(u32 index)struct amd_cpudata *cpudata =NULL ;union perf_cached cur_perf; -for_each_possible_cpu (cpu) { +for_each_online_cpu (cpu) { struct cpufreq_policy *policy __free(put_cpufreq_policy) = NULL; policy =cpufreq_cpu_get (cpu);if (!policy) -break ; +continue ; cpudata = policy->driver_data;if (get_shared_mem ()) {@@ -188,12 +188,12 @@ static int amd_pstate_ut_check_freq(u32 index)int cpu =0 ;struct amd_cpudata *cpudata =NULL ; -for_each_possible_cpu (cpu) { +for_each_online_cpu (cpu) { struct cpufreq_policy *policy __free(put_cpufreq_policy) = NULL; policy =cpufreq_cpu_get (cpu);if (!policy) -break ; +continue ; cpudata = policy->driver_data; if (!((policy->cpuinfo.max_freq >= cpudata->nominal_freq) &&Signature · 1 line
2.43.0
PATCH v3 11/18 cpufreq/amd-pstate-ut: Adjust variable scope for amd_pstate_ut_check_freq()
In reply to Mario LimoncielloFrom: Mario Limonciello <[email protected]>
The cpudata variable is only needed in the scope of the for loop. Move it there.
--- drivers/cpufreq/amd-pstate-ut.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/cpufreq/amd-pstate-ut.c +1 -1
@@ -186,10 +186,10 @@ static int amd_pstate_ut_check_perf(u32 index)static int amd_pstate_ut_check_freq (u32 index) {int cpu =0 ; -struct amd_cpudata *cpudata =NULL ;for_each_online_cpu (cpu) { struct cpufreq_policy *policy __free(put_cpufreq_policy) = NULL; +struct amd_cpudata *cpudata; policy =cpufreq_cpu_get (cpu);if (!policy)
Signature · 1 line
2.43.0
Re: [PATCH v3 11/18] cpufreq/amd-pstate-ut: Adjust variable scope for amd_pstate_ut_check_freq()
Quoted 16 lines · Mario Limonciello
From: Mario Limonciello <[email protected]>
The cpudata variable is only needed in the scope of the for loop. Move it there.
Reviewed-by Gautham R. Shenoy <[email protected]>Signed-off-by Mario Limonciello <[email protected]>--- drivers/cpufreq/amd-pstate-ut.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/cpufreq/amd-pstate-ut.c +0
-0
drivers/cpufreq/amd-pstate-ut.c static int amd_pstate_ut_check_perf(u32 index) · line 192
Quoted 8 lines
drivers/cpufreq/amd-pstate-ut.c +1
-1@@ -186,10 +186,10 @@ static int amd_pstate_ut_check_perf(u32 index)static int amd_pstate_ut_check_freq (u32 index) {int cpu =0 ; -struct amd_cpudata *cpudata =NULL ;for_each_online_cpu (cpu) { struct cpufreq_policy *policy __free(put_cpufreq_policy) = NULL; +struct amd_cpudata *cpudata;
I think we can do the same in "amd_pstate_ut_check_perf" as well,
With that taken care of,
Thanks,
Dhananjay
Quoted 3 lines
drivers/cpufreq/amd-pstate-ut.c +0
-0policy =cpufreq_cpu_get (cpu);if (!policy)
PATCH v3 12/18 cpufreq/amd-pstate: Replace all AMD_CPPC_* macros with masks
In reply to Mario LimoncielloFrom: Mario Limonciello <[email protected]>
Bitfield masks are easier to follow and less error prone.
---
v3:
* Add tag
* Add missing includes
v2:
* Add a comment in msr-index.h
* Pick up tag
--- arch/x86/include/asm/msr-index.h | 20 +++++++++++--------- arch/x86/kernel/acpi/cppc.c | 4 +++- drivers/cpufreq/amd-pstate-ut.c | 9 +++++---- drivers/cpufreq/amd-pstate.c | 16 ++++++---------- 4 files changed, 25 insertions(+), 24 deletions(-)
arch/x86/include/asm/msr-index.h +11 -9
@@ -701,15 +701,17 @@#define MSR_AMD_CPPC_REQ 0xc00102b3#define MSR_AMD_CPPC_STATUS 0xc00102b4 -#define AMD_CPPC_LOWEST_PERF (x) (((x) >> 0) & 0xff) -#define AMD_CPPC_LOWNONLIN_PERF (x) (((x) >> 8) & 0xff) -#define AMD_CPPC_NOMINAL_PERF (x) (((x) >> 16) & 0xff) -#define AMD_CPPC_HIGHEST_PERF (x) (((x) >> 24) & 0xff) - -#define AMD_CPPC_MAX_PERF (x) (((x) & 0xff) << 0) -#define AMD_CPPC_MIN_PERF (x) (((x) & 0xff) << 8) -#define AMD_CPPC_DES_PERF (x) (((x) & 0xff) << 16) -#define AMD_CPPC_ENERGY_PERF_PREF (x) (((x) & 0xff) << 24) +/* Masks for use with MSR_AMD_CPPC_CAP1 */ +#define AMD_CPPC_LOWEST_PERF_MASK GENMASK(7, 0) +#define AMD_CPPC_LOWNONLIN_PERF_MASK GENMASK(15, 8) +#define AMD_CPPC_NOMINAL_PERF_MASK GENMASK(23, 16) +#define AMD_CPPC_HIGHEST_PERF_MASK GENMASK(31, 24) + +/* Masks for use with MSR_AMD_CPPC_REQ */ +#define AMD_CPPC_MAX_PERF_MASK GENMASK(7, 0) +#define AMD_CPPC_MIN_PERF_MASK GENMASK(15, 8) +#define AMD_CPPC_DES_PERF_MASK GENMASK(23, 16) +#define AMD_CPPC_EPP_PERF_MASK GENMASK(31, 24)/* AMD Performance Counter Global Status and Control MSRs */ #define MSR_AMD64_PERF_CNTR_GLOBAL_STATUS 0xc0000300
arch/x86/kernel/acpi/cppc.c +3 -1
@@ -4,6 +4,8 @@* Copyright (c) 2016, Intel Corporation. */ +#include <linux/bitfield.h> +#include <acpi/cppc_acpi.h> #include <asm/msr.h> #include <asm/processor.h>
@@ -149,7 +151,7 @@ int amd_get_highest_perf(unsigned int cpu, u32 *highest_perf)if (ret) goto out; - val =AMD_CPPC_HIGHEST_PERF (val); + val =FIELD_GET (AMD_CPPC_HIGHEST_PERF_MASK , val); }else { ret =cppc_get_highest_perf (cpu, &val);if (ret)
drivers/cpufreq/amd-pstate-ut.c +5 -4
@@ -22,6 +22,7 @@#define pr_fmt (fmt) KBUILD_MODNAME ": " fmt +#include <linux/bitfield.h> #include <linux/kernel.h> #include <linux/module.h> #include <linux/moduleparam.h>
@@ -142,10 +143,10 @@ static int amd_pstate_ut_check_perf(u32 index)return ret; } - highest_perf =AMD_CPPC_HIGHEST_PERF (cap1); - nominal_perf =AMD_CPPC_NOMINAL_PERF (cap1); - lowest_nonlinear_perf =AMD_CPPC_LOWNONLIN_PERF (cap1); - lowest_perf =AMD_CPPC_LOWEST_PERF (cap1); + highest_perf =FIELD_GET (AMD_CPPC_HIGHEST_PERF_MASK , cap1); + nominal_perf =FIELD_GET (AMD_CPPC_NOMINAL_PERF_MASK , cap1); + lowest_nonlinear_perf =FIELD_GET (AMD_CPPC_LOWNONLIN_PERF_MASK , cap1); + lowest_perf =FIELD_GET (AMD_CPPC_LOWEST_PERF_MASK , cap1); } cur_perf =READ_ONCE (cpudata->perf);
drivers/cpufreq/amd-pstate.c +6 -10
@@ -89,11 +89,6 @@ static bool cppc_enabled;static bool amd_pstate_prefcore = true;static struct quirk_entry *quirks; -#define AMD_CPPC_MAX_PERF_MASK GENMASK(7, 0) -#define AMD_CPPC_MIN_PERF_MASK GENMASK(15, 8) -#define AMD_CPPC_DES_PERF_MASK GENMASK(23, 16) -#define AMD_CPPC_EPP_PERF_MASK GENMASK(31, 24) -/* * AMD Energy Preference Performance (EPP) * The EPP is used in the CCLK DPM controller to drive
@@ -439,12 +434,13 @@ static int msr_init_perf(struct amd_cpudata *cpudata) perf.highest_perf = numerator; perf.max_limit_perf = numerator; - perf.min_limit_perf =AMD_CPPC_LOWEST_PERF (cap1); - perf.nominal_perf =AMD_CPPC_NOMINAL_PERF (cap1); - perf.lowest_nonlinear_perf =AMD_CPPC_LOWNONLIN_PERF (cap1); - perf.lowest_perf =AMD_CPPC_LOWEST_PERF (cap1); + perf.min_limit_perf =FIELD_GET (AMD_CPPC_LOWEST_PERF_MASK , cap1); + perf.nominal_perf =FIELD_GET (AMD_CPPC_NOMINAL_PERF_MASK , cap1); + perf.lowest_nonlinear_perf =FIELD_GET (AMD_CPPC_LOWNONLIN_PERF_MASK , cap1); + perf.lowest_perf =FIELD_GET (AMD_CPPC_LOWEST_PERF_MASK , cap1);WRITE_ONCE (cpudata->perf, perf); -WRITE_ONCE (cpudata->prefcore_ranking,AMD_CPPC_HIGHEST_PERF (cap1)); +WRITE_ONCE (cpudata->prefcore_ranking,FIELD_GET (AMD_CPPC_HIGHEST_PERF_MASK , cap1)); +return 0 ; }
Signature · 1 line
2.43.0
PATCH v3 13/18 cpufreq/amd-pstate: Cache CPPC request in shared mem case too
In reply to Mario LimoncielloFrom: Mario Limonciello <[email protected]>
In order to prevent a potential write for shmem_update_perf() cache the request into the cppc_req_cached variable normally only used for the MSR case.
This adds symmetry into the code and potentially avoids extra writes.
--- drivers/cpufreq/amd-pstate.c | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-)
drivers/cpufreq/amd-pstate.c +21 -1
@@ -496,6 +496,8 @@ static int shmem_update_perf(struct amd_cpudata *cpudata, u8 min_perf, u8 des_perf, u8 max_perf, u8 epp, bool fast_switch) { struct cppc_perf_ctrls perf_ctrls; +u64 value, prev; +int ret;if (cppc_state ==AMD_PSTATE_ACTIVE ) {int ret =shmem_set_epp (cpudata, epp);
@@ -504,11 +506,29 @@ static int shmem_update_perf(struct amd_cpudata *cpudata, u8 min_perf,return ret; } + value = prev =READ_ONCE (cpudata->cppc_req_cached); + + value &= ~(AMD_CPPC_MAX_PERF_MASK |AMD_CPPC_MIN_PERF_MASK | +AMD_CPPC_DES_PERF_MASK |AMD_CPPC_EPP_PERF_MASK ); + value |=FIELD_PREP (AMD_CPPC_MAX_PERF_MASK , max_perf); + value |=FIELD_PREP (AMD_CPPC_DES_PERF_MASK , des_perf); + value |=FIELD_PREP (AMD_CPPC_MIN_PERF_MASK , min_perf); + value |=FIELD_PREP (AMD_CPPC_EPP_PERF_MASK , epp); + +if (value == prev) +return 0 ; + perf_ctrls.max_perf = max_perf; perf_ctrls.min_perf = min_perf; perf_ctrls.desired_perf = des_perf; -return cppc_set_perf (cpudata->cpu, &perf_ctrls); + ret =cppc_set_perf (cpudata->cpu, &perf_ctrls); +if (ret) +return ret; + +WRITE_ONCE (cpudata->cppc_req_cached, value); + +return 0 ; }static inline bool amd_pstate_sample (struct amd_cpudata *cpudata)
Signature · 1 line
2.43.0
PATCH v3 14/18 cpufreq/amd-pstate: Move all EPP tracing into *_update_perf and *_set_epp functions
In reply to Mario LimoncielloFrom: Mario Limonciello <[email protected]>
The EPP tracing is done by the caller today, but this precludes the information about whether the CPPC request has changed.
Move it into the update_perf and set_epp functions and include information about whether the request has changed from the last one. amd_pstate_update_perf() and amd_pstate_set_epp() now require the policy as an argument instead of the cpudata.
---
v3:
* Add tag
* Update commit message
--- drivers/cpufreq/amd-pstate-trace.h | 13 +++- drivers/cpufreq/amd-pstate.c | 116 ++++++++++++++++++----------- 2 files changed, 80 insertions(+), 49 deletions(-)
drivers/cpufreq/amd-pstate-trace.h +9 -4
@@ -90,7 +90,8 @@ TRACE_EVENT(amd_pstate_epp_perf,u8 epp, u8 min_perf, u8 max_perf, - bool boost + bool boost, + bool changed ), TP_ARGS(cpu_id,
@@ -98,7 +99,8 @@ TRACE_EVENT(amd_pstate_epp_perf, epp, min_perf, max_perf, - boost), + boost, + changed),TP_STRUCT__entry ( __field(unsigned int, cpu_id)
@@ -107,6 +109,7 @@ TRACE_EVENT(amd_pstate_epp_perf, __field(u8, min_perf) __field(u8, max_perf) __field(bool, boost) +__field (bool, changed) ), TP_fast_assign(
@@ -116,15 +119,17 @@ TRACE_EVENT(amd_pstate_epp_perf, __entry->min_perf = min_perf; __entry->max_perf = max_perf; __entry->boost = boost; + __entry->changed = changed; ), -TP_printk ("cpu%u: [%hhu<->%hhu]/%hhu, epp=%hhu, boost=%u" , +TP_printk ("cpu%u: [%hhu<->%hhu]/%hhu, epp=%hhu, boost=%u, changed=%u" , (unsigned int )__entry->cpu_id, (u8 )__entry->min_perf, (u8 )__entry->max_perf, (u8 )__entry->highest_perf, (u8 )__entry->epp, - (bool )__entry->boost + (bool )__entry->boost, + (bool )__entry->changed ) );
drivers/cpufreq/amd-pstate.c +71 -45
223 lines not on this page · raw message
Signature · 1 line
2.43.0
PATCH v3 15/18 cpufreq/amd-pstate: Update cppc_req_cached for shared mem EPP writes
In reply to Mario LimoncielloFrom: Mario Limonciello <[email protected]>
On EPP only writes update the cached variable so that the min/max performance controls don't need to be updated again.
--- drivers/cpufreq/amd-pstate.c | 6 ++++++ 1 file changed, 6 insertions(+)
drivers/cpufreq/amd-pstate.c +6 -0
@@ -336,6 +336,7 @@ static int shmem_set_epp(struct cpufreq_policy *policy, u8 epp) {struct amd_cpudata *cpudata = policy->driver_data;struct cppc_perf_ctrls perf_ctrls; +u64 value;int ret;if (trace_amd_pstate_epp_perf_enabled ()) {
@@ -362,6 +363,11 @@ static int shmem_set_epp(struct cpufreq_policy *policy, u8 epp) }WRITE_ONCE (cpudata->epp_cached, epp); + value =READ_ONCE (cpudata->cppc_req_cached); + value &= ~AMD_CPPC_EPP_PERF_MASK ; + value |=FIELD_PREP (AMD_CPPC_EPP_PERF_MASK , epp); +WRITE_ONCE (cpudata->cppc_req_cached, value); +return ret; }
Signature · 1 line
2.43.0
PATCH v3 16/18 cpufreq/amd-pstate: Drop debug statements for policy setting
In reply to Mario LimoncielloFrom: Mario Limonciello <[email protected]>
There are trace events that exist now for all amd-pstate modes that will output information right before programming to the hardware.
This makes the existing debug statements unnecessary remaining overhead. Drop them.
--- drivers/cpufreq/amd-pstate.c | 4 ---- 1 file changed, 4 deletions(-)
drivers/cpufreq/amd-pstate.c +0 -4
@@ -667,7 +667,6 @@ static int amd_pstate_verify(struct cpufreq_policy_data *policy_data) }cpufreq_verify_within_cpu_limits (policy_data); -pr_debug ("policy_max =%d, policy_min=%d\n" , policy_data->max, policy_data->min);return 0 ; }
@@ -1633,9 +1632,6 @@ static int amd_pstate_epp_set_policy(struct cpufreq_policy *policy)if (!policy->cpuinfo.max_freq)return -ENODEV ; -pr_debug ("set_policy: cpuinfo.max %u policy->max %u\n" , - policy->cpuinfo.max_freq, policy->max); - cpudata->policy = policy->policy; ret =amd_pstate_epp_update_limit (policy);
Signature · 1 line
2.43.0
PATCH v3 17/18 cpufreq/amd-pstate: Rework CPPC enabling
In reply to Mario LimoncielloFrom: Mario Limonciello <[email protected]>
The CPPC enable register is configured as "write once". That is any future writes don't actually do anything.
Because of this, all the cleanup paths that currently exist for CPPC disable are non-effective.
Rework CPPC enable to only enable after all the CAP registers have been read to avoid enabling CPPC on CPUs with invalid _CPC or unpopulated MSRs.
As the register is write once, remove all cleanup paths as well.
---
v3:
* Fixup for suspend/resume issue
--- drivers/cpufreq/amd-pstate.c | 185 ++++++++++++----------------------- 1 file changed, 62 insertions(+), 123 deletions(-)
drivers/cpufreq/amd-pstate.c +62 -123
@@ -85,7 +85,6 @@ static struct cpufreq_driver *current_pstate_driver;static struct cpufreq_driver amd_pstate_driver;static struct cpufreq_driver amd_pstate_epp_driver;static int cppc_state =AMD_PSTATE_UNDEFINED ; -static bool cppc_enabled;static bool amd_pstate_prefcore = true;static struct quirk_entry *quirks;
@@ -371,89 +370,40 @@ static int shmem_set_epp(struct cpufreq_policy *policy, u8 epp)return ret; } -static int amd_pstate_set_energy_pref_index (struct cpufreq_policy *policy, -int pref_index) +static inline int msr_cppc_enable (struct cpufreq_policy *policy) {struct amd_cpudata *cpudata = policy->driver_data; -u8 epp; - -if (!pref_index) - epp = cpudata->epp_default; -else - epp = epp_values[pref_index]; -if (epp >0 && cpudata->policy ==CPUFREQ_POLICY_PERFORMANCE ) { -pr_debug ("EPP cannot be set under performance policy\n" ); -return -EBUSY ; - } - -return amd_pstate_set_epp (policy, epp); -} - -static inline int msr_cppc_enable (bool enable) -{ -int ret, cpu; -unsigned long logical_proc_id_mask =0 ; - -/* -* MSR_AMD_CPPC_ENABLE is write-once, once set it cannot be cleared. -*/ -if (!enable) -return 0 ; - -if (enable == cppc_enabled) -return 0 ; - -for_each_present_cpu (cpu) { -unsigned long logical_id =topology_logical_package_id (cpu); - -if (test_bit (logical_id, &logical_proc_id_mask)) -continue ; - -set_bit (logical_id, &logical_proc_id_mask); - - ret =wrmsrl_safe_on_cpu (cpu,MSR_AMD_CPPC_ENABLE , - enable); -if (ret) -return ret; - } - - cppc_enabled = enable; -return 0 ; +return wrmsrl_safe_on_cpu (cpudata->cpu,MSR_AMD_CPPC_ENABLE ,1 ); } -static int shmem_cppc_enable (bool enable) +static int shmem_cppc_enable (struct cpufreq_policy *policy) { -int cpu, ret =0 ; +struct amd_cpudata *cpudata = policy->driver_data;struct cppc_perf_ctrls perf_ctrls; +int ret; -if (enable == cppc_enabled) -return 0 ; + ret =cppc_set_enable (cpudata->cpu,1 ); +if (ret) +return ret; -for_each_present_cpu (cpu) { - ret =cppc_set_enable (cpu, enable); +/* Enable autonomous mode for EPP */ +if (cppc_state ==AMD_PSTATE_ACTIVE ) { +/* Set desired perf as zero to allow EPP firmware control */ + perf_ctrls.desired_perf =0 ; + ret =cppc_set_perf (cpudata->cpu, &perf_ctrls);if (ret)return ret; - -/* Enable autonomous mode for EPP */ -if (cppc_state ==AMD_PSTATE_ACTIVE ) { -/* Set desired perf as zero to allow EPP firmware control */ - perf_ctrls.desired_perf =0 ; - ret =cppc_set_perf (cpu, &perf_ctrls); -if (ret) -return ret; - } } - cppc_enabled = enable;return ret; }DEFINE_STATIC_CALL (amd_pstate_cppc_enable, msr_cppc_enable); -static inline int amd_pstate_cppc_enable (bool enable) +static inline int amd_pstate_cppc_enable (struct cpufreq_policy *policy) { -return static_call (amd_pstate_cppc_enable)(enable); +return static_call (amd_pstate_cppc_enable)(policy); }static int msr_init_perf (struct amd_cpudata *cpudata)
@@ -1115,24 +1065,7 @@ static void amd_pstate_cpu_exit(struct cpufreq_policy *policy)static int amd_pstate_cpu_resume (struct cpufreq_policy *policy) { -int ret; - - ret =amd_pstate_cppc_enable (true); -if (ret) -pr_err ("failed to enable amd-pstate during resume, return %d\n" , ret); - -return ret; -} - -static int amd_pstate_cpu_suspend (struct cpufreq_policy *policy) -{ -int ret; - - ret =amd_pstate_cppc_enable (false); -if (ret) -pr_err ("failed to disable amd-pstate during suspend, return %d\n" , ret); - -return ret; +return amd_pstate_cppc_enable (policy); }/* Sysfs attributes */
@@ -1226,8 +1159,10 @@ static ssize_t show_energy_performance_available_preferences(static ssize_t store_energy_performance_preference (struct cpufreq_policy *policy,const char *buf,size_t count) { +struct amd_cpudata *cpudata = policy->driver_data;char str_preference[21 ];ssize_t ret; +u8 epp; ret =sscanf (buf,"%20s" , str_preference);if (ret !=1 )
@@ -1237,7 +1172,29 @@ static ssize_t store_energy_performance_preference(if (ret <0 )return -EINVAL ; - ret =amd_pstate_set_energy_pref_index (policy, ret); +if (!ret) + epp = cpudata->epp_default; +else + epp = epp_values[ret]; + +if (epp >0 && policy->policy ==CPUFREQ_POLICY_PERFORMANCE ) { +pr_debug ("EPP cannot be set under performance policy\n" ); +return -EBUSY ; + } + +if (trace_amd_pstate_epp_perf_enabled ()) { +union perf_cached perf = cpudata->perf; + +trace_amd_pstate_epp_perf (cpudata->cpu, perf.highest_perf, + epp, +FIELD_GET (AMD_CPPC_MIN_PERF_MASK , cpudata->cppc_req_cached), +FIELD_GET (AMD_CPPC_MAX_PERF_MASK , cpudata->cppc_req_cached), + policy->boost_enabled, +FIELD_GET (AMD_CPPC_EPP_PERF_MASK , + cpudata->cppc_req_cached) != epp); + } + + ret =amd_pstate_set_epp (policy, epp);return ret ? ret : count; }
@@ -1270,7 +1227,6 @@ static ssize_t show_energy_performance_preference(static void amd_pstate_driver_cleanup (void ) { -amd_pstate_cppc_enable (false); cppc_state =AMD_PSTATE_DISABLE ; current_pstate_driver =NULL ; }
@@ -1304,14 +1260,6 @@ static int amd_pstate_register_driver(int mode) cppc_state = mode; - ret =amd_pstate_cppc_enable (true); -if (ret) { -pr_err ("failed to enable cppc during amd-pstate driver registration, return %d\n" , - ret); -amd_pstate_driver_cleanup (); -return ret; - } -/* at least one CPU supports CPB */ current_pstate_driver->boost_enabled =cpu_feature_enabled (X86_FEATURE_CPB );
@@ -1551,11 +1499,15 @@ static int amd_pstate_epp_cpu_init(struct cpufreq_policy *policy) policy->cpuinfo.max_freq = policy->max =perf_to_freq (perf, cpudata->nominal_freq, perf.highest_perf); + policy->driver_data = cpudata; + + ret =amd_pstate_cppc_enable (policy); +if (ret) + goto free_cpudata1;/* It will be updated by governor */ policy->cur = policy->cpuinfo.min_freq; - policy->driver_data = cpudata; policy->boost_enabled =READ_ONCE (cpudata->boost_supported);
@@ -1647,33 +1599,27 @@ static int amd_pstate_epp_set_policy(struct cpufreq_policy *policy)return 0 ; } -static int amd_pstate_epp_reenable (struct cpufreq_policy *policy) +static int amd_pstate_epp_cpu_online (struct cpufreq_policy *policy) {struct amd_cpudata *cpudata = policy->driver_data;union perf_cached perf =READ_ONCE (cpudata->perf);int ret; - ret =amd_pstate_cppc_enable (true); -if (ret) -pr_err ("failed to enable amd pstate during resume, return %d\n" , ret); - - -return amd_pstate_epp_update_limit (policy); -} +pr_debug ("AMD CPU Core %d going online\n" , cpudata->cpu); -static int amd_pstate_epp_cpu_online (struct cpufreq_policy *policy) -{ -struct amd_cpudata *cpudata = policy->driver_data; -int ret; + ret =amd_pstate_cppc_enable (policy); +if (ret) +return ret; -pr_debug ("AMD CPU Core %d going online\n" , cpudata->cpu); - ret =amd_pstate_epp_reenable (policy); + ret =amd_pstate_update_perf (policy,0 ,0 , perf.highest_perf, cpudata->epp_cached, false);if (ret)return ret; + cpudata->suspended = false;return 0 ; + }static int amd_pstate_epp_cpu_offline (struct cpufreq_policy *policy)
@@ -1691,11 +1637,6 @@ static int amd_pstate_epp_cpu_offline(struct cpufreq_policy *policy)static int amd_pstate_epp_suspend (struct cpufreq_policy *policy) {struct amd_cpudata *cpudata = policy->driver_data; -int ret; - -/* avoid suspending when EPP is not enabled */ -if (cppc_state !=AMD_PSTATE_ACTIVE ) -return 0 ;/* invalidate to ensure it's rewritten during resume */ cpudata->cppc_req_cached =0 ;
@@ -1703,11 +1644,6 @@ static int amd_pstate_epp_suspend(struct cpufreq_policy *policy)/* set this flag to avoid setting core offline*/ cpudata->suspended = true; -/* disable CPPC in lowlevel firmware */ - ret =amd_pstate_cppc_enable (false); -if (ret) -pr_err ("failed to suspend, return %d\n" , ret); -return 0 ; }
@@ -1716,8 +1652,13 @@ static int amd_pstate_epp_resume(struct cpufreq_policy *policy)struct amd_cpudata *cpudata = policy->driver_data;if (cpudata->suspended) { +union perf_cached perf =READ_ONCE (cpudata->perf); +int ret; +/* enable amd pstate from suspend state*/ -amd_pstate_epp_reenable (policy); + ret =amd_pstate_epp_update_limit (policy); +if (ret) +return ret; cpudata->suspended = false; }
@@ -1732,7 +1673,6 @@ static struct cpufreq_driver amd_pstate_driver = { .fast_switch = amd_pstate_fast_switch, .init = amd_pstate_cpu_init, .exit = amd_pstate_cpu_exit, - .suspend = amd_pstate_cpu_suspend, .resume = amd_pstate_cpu_resume, .set_boost = amd_pstate_set_boost, .update_limits = amd_pstate_update_limits,
@@ -1748,8 +1688,8 @@ static struct cpufreq_driver amd_pstate_epp_driver = { .exit = amd_pstate_epp_cpu_exit, .offline = amd_pstate_epp_cpu_offline, .online = amd_pstate_epp_cpu_online, - .suspend = amd_pstate_epp_suspend, - .resume = amd_pstate_epp_resume, + .suspend = amd_pstate_epp_suspend, + .resume = amd_pstate_epp_resume, .update_limits = amd_pstate_update_limits, .set_boost = amd_pstate_set_boost, .name = "amd-pstate-epp",
@@ -1900,7 +1840,6 @@ static int __init amd_pstate_init(void) global_attr_free:cpufreq_unregister_driver (current_pstate_driver); -amd_pstate_cppc_enable (false);return ret; }device_initcall (amd_pstate_init);
Signature · 1 line
2.43.0
Re: [PATCH v3 17/18] cpufreq/amd-pstate: Rework CPPC enabling
Quoted 19 lines · Mario Limonciello
From: Mario Limonciello <[email protected]>
The CPPC enable register is configured as "write once". That is any future writes don't actually do anything.
Because of this, all the cleanup paths that currently exist for CPPC disable are non-effective.
Rework CPPC enable to only enable after all the CAP registers have been read to avoid enabling CPPC on CPUs with invalid
_CPCor unpopulated MSRs.As the register is write once, remove all cleanup paths as well.
Signed-off-by Mario Limonciello <[email protected]>---
v3:
* Fixup for suspend/resume issue
---
[..snip..]
Quoted 14 lines
drivers/cpufreq/amd-pstate.c +6
-4-static int shmem_cppc_enable (bool enable) +static int shmem_cppc_enable (struct cpufreq_policy *policy) { -int cpu, ret =0 ; +struct amd_cpudata *cpudata = policy->driver_data;struct cppc_perf_ctrls perf_ctrls; +int ret; -if (enable == cppc_enabled) -return 0 ; + ret =cppc_set_enable (cpudata->cpu,1 ); +if (ret) +return ret;
drivers/cpufreq/amd-pstate.c static int shmem_set_epp(struct cpufreq_policy *policy, u8 epp) · line 396
Quoted 10 lines
drivers/cpufreq/amd-pstate.c +5
-2-for_each_present_cpu (cpu) { - ret =cppc_set_enable (cpu, enable); +/* Enable autonomous mode for EPP */ +if (cppc_state ==AMD_PSTATE_ACTIVE ) { +/* Set desired perf as zero to allow EPP firmware control */ + perf_ctrls.desired_perf =0 ; + ret =cppc_set_perf (cpudata->cpu, &perf_ctrls);if (ret)return ret;
We don't need the if condition here. There is nothing following this inside the if block and the function return "ret" soon after coming out of this if block.
Quoted 18 lines
drivers/cpufreq/amd-pstate.c +0
-11- -/* Enable autonomous mode for EPP */ -if (cppc_state ==AMD_PSTATE_ACTIVE ) { -/* Set desired perf as zero to allow EPP firmware control */ - perf_ctrls.desired_perf =0 ; - ret =cppc_set_perf (cpu, &perf_ctrls); -if (ret) -return ret; - } } - cppc_enabled = enable;return ret; }DEFINE_STATIC_CALL (amd_pstate_cppc_enable, msr_cppc_enable); -static inline int amd_pstate_cppc_enable (bool enable)
[..snip..]
Quoted 19 lines
drivers/cpufreq/amd-pstate.c +2
-10-static int amd_pstate_epp_reenable (struct cpufreq_policy *policy) +static int amd_pstate_epp_cpu_online (struct cpufreq_policy *policy) {struct amd_cpudata *cpudata = policy->driver_data;union perf_cached perf =READ_ONCE (cpudata->perf);int ret; - ret =amd_pstate_cppc_enable (true); -if (ret) -pr_err ("failed to enable amd pstate during resume, return %d\n" , ret); - - -return amd_pstate_epp_update_limit (policy); -} +pr_debug ("AMD CPU Core %d going online\n" , cpudata->cpu); -static int amd_pstate_epp_cpu_online (struct cpufreq_policy *policy) -{
drivers/cpufreq/amd-pstate.c static int amd_pstate_epp_set_policy(struct cpufreq_policy *policy) · line 1615
Quoted 10 lines
drivers/cpufreq/amd-pstate.c +4
-4-struct amd_cpudata *cpudata = policy->driver_data; -int ret; + ret =amd_pstate_cppc_enable (policy); +if (ret) +return ret; -pr_debug ("AMD CPU Core %d going online\n" , cpudata->cpu); - ret =amd_pstate_epp_reenable (policy); + ret =amd_pstate_update_perf (policy,0 ,0 , perf.highest_perf, cpudata->epp_cached, false);
Previously, when a CPU came online, the callpath would be amd_pstate_epp_cpu_online(policy)
--> amd_pstate_epp_reenable(policy)
--> amd_pstate_epp_update_limit(policy)
--> amd_pstate_epp_update_limit(policy)which reevaluates the min_perf_limit and max_perf_limit based on policy->min and policy->max and then calls
amd_pstate_update_perf(policy, min_limit_perf, 0, max_limit_perf, epp, false)
With this patch, we call
amd_pstate_update_perf(policy, 0, 0, perf.highest_perf, cpudata->epp_cached, false);
which would set CPPC.min_perf to 0.
I guess this should be ok since cpufreq_online() would eventually call amd_pstate_verify() and amd_pstate_epp_set_policy() which should re-initialize the the min_limit_perf and max_limit_perf. Though I haven't verified if the behaviour changes with this patch when the CPU is offlined and brought back online.
Rest of the patch looks good to me.
Signature · 2 lines
Thanks and Regards gautham.
Re: [PATCH v3 17/18] cpufreq/amd-pstate: Rework CPPC enabling
Quoted 117 lines · Gautham R. Shenoy
Quoted 19 lines · Mario Limonciello
From: Mario Limonciello <[email protected]>
The CPPC enable register is configured as "write once". That is any future writes don't actually do anything.
Because of this, all the cleanup paths that currently exist for CPPC disable are non-effective.
Rework CPPC enable to only enable after all the CAP registers have been read to avoid enabling CPPC on CPUs with invalid
_CPCor unpopulated MSRs.As the register is write once, remove all cleanup paths as well.
Signed-off-by Mario Limonciello <[email protected]>---
v3:
* Fixup for suspend/resume issue
---[..snip..]
Quoted 14 lines
drivers/cpufreq/amd-pstate.c +6
-4-static int shmem_cppc_enable (bool enable) +static int shmem_cppc_enable (struct cpufreq_policy *policy) { -int cpu, ret =0 ; +struct amd_cpudata *cpudata = policy->driver_data;struct cppc_perf_ctrls perf_ctrls; +int ret; -if (enable == cppc_enabled) -return 0 ; + ret =cppc_set_enable (cpudata->cpu,1 ); +if (ret) +return ret;drivers/cpufreq/amd-pstate.c static int shmem_set_epp(struct cpufreq_policy *policy, u8 epp) · line 396
Quoted 10 lines
drivers/cpufreq/amd-pstate.c +5
-2-for_each_present_cpu (cpu) { - ret =cppc_set_enable (cpu, enable); +/* Enable autonomous mode for EPP */ +if (cppc_state ==AMD_PSTATE_ACTIVE ) { +/* Set desired perf as zero to allow EPP firmware control */ + perf_ctrls.desired_perf =0 ; + ret =cppc_set_perf (cpudata->cpu, &perf_ctrls);if (ret)return ret;We don't need the if condition here. There is nothing following this inside the if block and the function return "ret" soon after coming out of this if block.
Quoted 18 lines
drivers/cpufreq/amd-pstate.c +0
-11- -/* Enable autonomous mode for EPP */ -if (cppc_state ==AMD_PSTATE_ACTIVE ) { -/* Set desired perf as zero to allow EPP firmware control */ - perf_ctrls.desired_perf =0 ; - ret =cppc_set_perf (cpu, &perf_ctrls); -if (ret) -return ret; - } } - cppc_enabled = enable;return ret; }DEFINE_STATIC_CALL (amd_pstate_cppc_enable, msr_cppc_enable); -static inline int amd_pstate_cppc_enable (bool enable)[..snip..]
Quoted 19 lines
drivers/cpufreq/amd-pstate.c +2
-10-static int amd_pstate_epp_reenable (struct cpufreq_policy *policy) +static int amd_pstate_epp_cpu_online (struct cpufreq_policy *policy) {struct amd_cpudata *cpudata = policy->driver_data;union perf_cached perf =READ_ONCE (cpudata->perf);int ret; - ret =amd_pstate_cppc_enable (true); -if (ret) -pr_err ("failed to enable amd pstate during resume, return %d\n" , ret); - - -return amd_pstate_epp_update_limit (policy); -} +pr_debug ("AMD CPU Core %d going online\n" , cpudata->cpu); -static int amd_pstate_epp_cpu_online (struct cpufreq_policy *policy) -{drivers/cpufreq/amd-pstate.c static int amd_pstate_epp_set_policy(struct cpufreq_policy *policy) · line 1615
Quoted 10 lines
drivers/cpufreq/amd-pstate.c +4
-4-struct amd_cpudata *cpudata = policy->driver_data; -int ret; + ret =amd_pstate_cppc_enable (policy); +if (ret) +return ret; -pr_debug ("AMD CPU Core %d going online\n" , cpudata->cpu); - ret =amd_pstate_epp_reenable (policy); + ret =amd_pstate_update_perf (policy,0 ,0 , perf.highest_perf, cpudata->epp_cached, false);Previously, when a CPU came online, the callpath would be
amd_pstate_epp_cpu_online(policy)
-->amd_pstate_epp_reenable(policy)--> amd_pstate_epp_update_limit(policy) --> amd_pstate_epp_update_limit(policy)which reevaluates the
min_perf_limitandmax_perf_limitbased onpolicy->minandpolicy->maxand then calls
amd_pstate_update_perf(policy, min_limit_perf, 0, max_limit_perf, epp, false)With this patch, we call
amd_pstate_update_perf(policy, 0, 0, perf.highest_perf, cpudata->epp_cached, false);
Quoted 7 lines
which would set CPPC.min_perf to 0.
I guess this should be ok since
cpufreq_online()would eventually callamd_pstate_verify()andamd_pstate_epp_set_policy()which should re-initialize the themin_limit_perfandmax_limit_perf. Though I haven't verified if the behaviour changes with this patch when the CPU is offlined and brought back online.
I'll double check with removing amd_pstate_update_perf() call from amd_pstate_epp_cpu_online(). I think it will be clearer to let it get set from the amd_pstate_epp_set_policy() call.
PATCH v3 18/18 cpufreq/amd-pstate: Stop caching EPP
In reply to Mario LimoncielloFrom: Mario Limonciello <[email protected]>
EPP values are cached in the cpudata structure per CPU. This is needless though because they are also cached in the CPPC request variable.
Drop the separate cache for EPP values and always reference the CPPC request variable when needed.
--- drivers/cpufreq/amd-pstate.c | 27 ++++++++++++++------------- drivers/cpufreq/amd-pstate.h | 1 - 2 files changed, 14 insertions(+), 14 deletions(-)
drivers/cpufreq/amd-pstate.c +14 -13
@@ -268,8 +268,6 @@ static int msr_update_perf(struct cpufreq_policy *policy, u8 min_perf, }WRITE_ONCE (cpudata->cppc_req_cached, value); -if (epp != cpudata->epp_cached) -WRITE_ONCE (cpudata->epp_cached, epp);return 0 ; }
@@ -318,7 +316,6 @@ static int msr_set_epp(struct cpufreq_policy *policy, u8 epp) }/* update both so that msr_update_perf() can effectively check */ -WRITE_ONCE (cpudata->epp_cached, epp);WRITE_ONCE (cpudata->cppc_req_cached, value);return ret;
@@ -335,9 +332,12 @@ static int shmem_set_epp(struct cpufreq_policy *policy, u8 epp) {struct amd_cpudata *cpudata = policy->driver_data;struct cppc_perf_ctrls perf_ctrls; +u8 epp_cached;u64 value;int ret; + + epp_cached =FIELD_GET (AMD_CPPC_EPP_PERF_MASK , cpudata->cppc_req_cached);if (trace_amd_pstate_epp_perf_enabled ()) {union perf_cached perf = cpudata->perf;
@@ -348,10 +348,10 @@ static int shmem_set_epp(struct cpufreq_policy *policy, u8 epp)FIELD_GET (AMD_CPPC_MAX_PERF_MASK , cpudata->cppc_req_cached), policy->boost_enabled, - epp != cpudata->epp_cached); + epp != epp_cached); } -if (epp == cpudata->epp_cached) +if (epp == epp_cached)return 0 ; perf_ctrls.energy_perf = epp;
@@ -360,7 +360,6 @@ static int shmem_set_epp(struct cpufreq_policy *policy, u8 epp)pr_debug ("failed to set energy perf value (%d)\n" , ret);return ret; } -WRITE_ONCE (cpudata->epp_cached, epp); value =READ_ONCE (cpudata->cppc_req_cached); value &= ~AMD_CPPC_EPP_PERF_MASK ;
@@ -1203,9 +1202,11 @@ static ssize_t show_energy_performance_preference( struct cpufreq_policy *policy, char *buf) { struct amd_cpudata *cpudata = policy->driver_data; -u8 preference; +u8 preference, epp; + + epp =FIELD_GET (AMD_CPPC_EPP_PERF_MASK , cpudata->cppc_req_cached); -switch (cpudata->epp_cached) { +switch (epp) {case AMD_CPPC_EPP_PERFORMANCE : preference =EPP_INDEX_PERFORMANCE ;break ;
@@ -1568,7 +1569,7 @@ static int amd_pstate_epp_update_limit(struct cpufreq_policy *policy)if (cpudata->policy ==CPUFREQ_POLICY_PERFORMANCE ) epp =0 ;else - epp =READ_ONCE (cpudata->epp_cached); + epp =FIELD_GET (AMD_CPPC_EPP_PERF_MASK , cpudata->cppc_req_cached); perf =READ_ONCE (cpudata->perf);
@@ -1604,22 +1605,22 @@ static int amd_pstate_epp_cpu_online(struct cpufreq_policy *policy)struct amd_cpudata *cpudata = policy->driver_data;union perf_cached perf =READ_ONCE (cpudata->perf);int ret; +u8 epp; + + epp =FIELD_GET (AMD_CPPC_EPP_PERF_MASK , cpudata->cppc_req_cached);pr_debug ("AMD CPU Core %d going online\n" , cpudata->cpu); ret =amd_pstate_cppc_enable (policy);if (ret)return ret; - - - ret =amd_pstate_update_perf (policy,0 ,0 , perf.highest_perf, cpudata->epp_cached, false); + ret =amd_pstate_update_perf (policy,0 ,0 , perf.highest_perf, epp, false);if (ret)return ret; cpudata->suspended = false;return 0 ; - }static int amd_pstate_epp_cpu_offline (struct cpufreq_policy *policy)
drivers/cpufreq/amd-pstate.h +0 -1
@@ -100,7 +100,6 @@ struct amd_cpudata {bool hw_prefcore;/* EPP feature related attributes*/ -u8 epp_cached;u32 policy;bool suspended;u8 epp_default;
Signature · 1 line
2.43.0
Re: [PATCH v3 18/18] cpufreq/amd-pstate: Stop caching EPP
Quoted 10 lines · Mario Limonciello
From: Mario Limonciello <[email protected]>
EPP values are cached in the cpudata structure per CPU. This is needless though because they are also cached in the CPPC request variable.
Drop the separate cache for EPP values and always reference the CPPC request variable when needed.
Reviewed-by Dhananjay Ugwekar <[email protected]>Signed-off-by Mario Limonciello <[email protected]>
LGTM
Signature · 2 lines
Thanks and Regards gautham.
Quoted 125 lines
--- drivers/cpufreq/amd-pstate.c | 27 ++++++++++++++------------- drivers/cpufreq/amd-pstate.h | 1 - 2 files changed, 14 insertions(+), 14 deletions(-)drivers/cpufreq/amd-pstate.c +14
-13@@ -268,8 +268,6 @@ static int msr_update_perf(struct cpufreq_policy *policy, u8 min_perf, }WRITE_ONCE (cpudata->cppc_req_cached, value); -if (epp != cpudata->epp_cached) -WRITE_ONCE (cpudata->epp_cached, epp);return 0 ; }@@ -318,7 +316,6 @@ static int msr_set_epp(struct cpufreq_policy *policy, u8 epp) }/* update both so that msr_update_perf() can effectively check */ -WRITE_ONCE (cpudata->epp_cached, epp);WRITE_ONCE (cpudata->cppc_req_cached, value);return ret;@@ -335,9 +332,12 @@ static int shmem_set_epp(struct cpufreq_policy *policy, u8 epp) {struct amd_cpudata *cpudata = policy->driver_data;struct cppc_perf_ctrls perf_ctrls; +u8 epp_cached;u64 value;int ret; + + epp_cached =FIELD_GET (AMD_CPPC_EPP_PERF_MASK , cpudata->cppc_req_cached);if (trace_amd_pstate_epp_perf_enabled ()) {union perf_cached perf = cpudata->perf;@@ -348,10 +348,10 @@ static int shmem_set_epp(struct cpufreq_policy *policy, u8 epp)FIELD_GET (AMD_CPPC_MAX_PERF_MASK , cpudata->cppc_req_cached), policy->boost_enabled, - epp != cpudata->epp_cached); + epp != epp_cached); } -if (epp == cpudata->epp_cached) +if (epp == epp_cached)return 0 ; perf_ctrls.energy_perf = epp;@@ -360,7 +360,6 @@ static int shmem_set_epp(struct cpufreq_policy *policy, u8 epp)pr_debug ("failed to set energy perf value (%d)\n" , ret);return ret; } -WRITE_ONCE (cpudata->epp_cached, epp); value =READ_ONCE (cpudata->cppc_req_cached); value &= ~AMD_CPPC_EPP_PERF_MASK ;@@ -1203,9 +1202,11 @@ static ssize_t show_energy_performance_preference( struct cpufreq_policy *policy, char *buf) { struct amd_cpudata *cpudata = policy->driver_data; -u8 preference; +u8 preference, epp; + + epp =FIELD_GET (AMD_CPPC_EPP_PERF_MASK , cpudata->cppc_req_cached); -switch (cpudata->epp_cached) { +switch (epp) {case AMD_CPPC_EPP_PERFORMANCE : preference =EPP_INDEX_PERFORMANCE ;break ;@@ -1568,7 +1569,7 @@ static int amd_pstate_epp_update_limit(struct cpufreq_policy *policy)if (cpudata->policy ==CPUFREQ_POLICY_PERFORMANCE ) epp =0 ;else - epp =READ_ONCE (cpudata->epp_cached); + epp =FIELD_GET (AMD_CPPC_EPP_PERF_MASK , cpudata->cppc_req_cached); perf =READ_ONCE (cpudata->perf);@@ -1604,22 +1605,22 @@ static int amd_pstate_epp_cpu_online(struct cpufreq_policy *policy)struct amd_cpudata *cpudata = policy->driver_data;union perf_cached perf =READ_ONCE (cpudata->perf);int ret; +u8 epp; + + epp =FIELD_GET (AMD_CPPC_EPP_PERF_MASK , cpudata->cppc_req_cached);pr_debug ("AMD CPU Core %d going online\n" , cpudata->cpu); ret =amd_pstate_cppc_enable (policy);if (ret)return ret; - - - ret =amd_pstate_update_perf (policy,0 ,0 , perf.highest_perf, cpudata->epp_cached, false); + ret =amd_pstate_update_perf (policy,0 ,0 , perf.highest_perf, epp, false);if (ret)return ret; cpudata->suspended = false;return 0 ; - }static int amd_pstate_epp_cpu_offline (struct cpufreq_policy *policy)drivers/cpufreq/amd-pstate.h +0
-1@@ -100,7 +100,6 @@ struct amd_cpudata {bool hw_prefcore;/* EPP feature related attributes*/ -u8 epp_cached;u32 policy;bool suspended;u8 epp_default;Signature · 1 line
2.43.0