[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YxlC6F8NVeY1Gv27@amd.com>
Date: Thu, 8 Sep 2022 09:18:32 +0800
From: Huang Rui <ray.huang@....com>
To: "Meng, Li (Jassmine)" <Li.Meng@....com>
Cc: Shuah Khan <skhan@...uxfoundation.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
"Fontenot, Nathan" <Nathan.Fontenot@....com>,
"Sharma, Deepak" <Deepak.Sharma@....com>,
"Deucher, Alexander" <Alexander.Deucher@....com>,
"Limonciello, Mario" <Mario.Limonciello@....com>,
"Su, Jinzhou (Joe)" <Jinzhou.Su@....com>,
"Yuan, Perry" <Perry.Yuan@....com>,
"Du, Xiaojian" <Xiaojian.Du@....com>,
Viresh Kumar <viresh.kumar@...aro.org>,
Borislav Petkov <bp@...en8.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RESEND PATCH] cpufreq: amd-pstate: Add explanation for
X86_AMD_PSTATE_UT
On Thu, Sep 08, 2022 at 08:28:21AM +0800, Meng, Li (Jassmine) wrote:
> This kernel module is used for testing. It's safe to say M here.
> It can also be built-in without X86_AMD_PSTATE enabled.
> Currently, only tests for amd-pstate are supported. If X86_AMD_PSTATE
> is set disabled, it can tell the users test can only run on amd-pstate
> driver, please set X86_AMD_PSTATE enabled.
> In the future, comparison tests will be added. It can set amd-pstate
> disabled and set acpi-cpufreq enabled to run test cases, then compare
> the test results.
>
> Suggested-by: Shuah Khan <skhan@...uxfoundation.org>
> Signed-off-by: Meng Li <li.meng@....com>
Patch looks very good for me. Please feel free to add
Acked-by: Huang Rui <ray.huang@....com>
> ---
> drivers/cpufreq/Kconfig.x86 | 8 ++++++++
> tools/testing/selftests/amd-pstate/amd-pstate-ut.sh | 1 +
> 2 files changed, 9 insertions(+)
>
> diff --git a/drivers/cpufreq/Kconfig.x86 b/drivers/cpufreq/Kconfig.x86
> index fdd819069d72..310779b07daf 100644
> --- a/drivers/cpufreq/Kconfig.x86
> +++ b/drivers/cpufreq/Kconfig.x86
> @@ -58,6 +58,14 @@ config X86_AMD_PSTATE_UT
> help
> This kernel module is used for testing. It's safe to say M here.
>
> + It can also be built-in without X86_AMD_PSTATE enabled.
> + Currently, only tests for amd-pstate are supported. If X86_AMD_PSTATE
> + is set disabled, it can tell the users test can only run on amd-pstate
> + driver, please set X86_AMD_PSTATE enabled.
> + In the future, comparison tests will be added. It can set amd-pstate
> + disabled and set acpi-cpufreq enabled to run test cases, then compare
> + the test results.
> +
> config X86_ACPI_CPUFREQ
> tristate "ACPI Processor P-States driver"
> depends on ACPI_PROCESSOR
> diff --git a/tools/testing/selftests/amd-pstate/amd-pstate-ut.sh b/tools/testing/selftests/amd-pstate/amd-pstate-ut.sh
> index 273364650285..f8e82d91ffcf 100755
> --- a/tools/testing/selftests/amd-pstate/amd-pstate-ut.sh
> +++ b/tools/testing/selftests/amd-pstate/amd-pstate-ut.sh
> @@ -32,6 +32,7 @@ fi
> scaling_driver=$(cat /sys/devices/system/cpu/cpufreq/policy0/scaling_driver)
> if [ "$scaling_driver" != "amd-pstate" ]; then
> echo "$0 # Skipped: Test can only run on amd-pstate driver."
> + echo "$0 # Please set X86_AMD_PSTATE enabled."
> echo "$0 # Current cpufreq scaling drvier is $scaling_driver."
> exit $ksft_skip
> fi
> --
> 2.34.1
>
Powered by blists - more mailing lists