[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240626042043.2410-1-mario.limonciello@amd.com>
Date: Tue, 25 Jun 2024 23:20:41 -0500
From: Mario Limonciello <mario.limonciello@....com>
To: Borislav Petkov <bp@...en8.de>, "Gautham R . Shenoy"
<gautham.shenoy@....com>, Perry Yuan <perry.yuan@....com>
CC: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
"Dave Hansen" <dave.hansen@...ux.intel.com>, "maintainer:X86 ARCHITECTURE
(32-BIT AND 64-BIT)" <x86@...nel.org>, "H . Peter Anvin" <hpa@...or.com>,
Huang Rui <ray.huang@....com>, Mario Limonciello <mario.limonciello@....com>,
"Rafael J . Wysocki" <rafael@...nel.org>, Viresh Kumar
<viresh.kumar@...aro.org>, Nikolay Borisov <nik.borisov@...e.com>, Peter
Zijlstra <peterz@...radead.org>, "open list:X86 ARCHITECTURE (32-BIT AND
64-BIT)" <linux-kernel@...r.kernel.org>, "open list:AMD PSTATE DRIVER"
<linux-pm@...r.kernel.org>
Subject: [PATCH 0/2] Fixes for wrong performance levels in acpi-cpufreq
In testing with amd-pstate disabled, I noticed that family 0x19 model 0x70
(Phoenix) was reporting an inccorrect max frequency. This is because the
perf levels used to look it up are wrong.
The correct values are stored in amd-pstate, but there is no reason to
store it in two places. Move the amd-pstate values over to one place
so that both drivers get the right values.
Mario Limonciello (2):
x86/cpu/amd: Clarify amd_get_highest_perf()
cpufreq: amd-pstate: Use amd_get_highest_perf() to lookup perf values
arch/x86/kernel/cpu/amd.c | 44 ++++++++++++++++++++++++++++++------
drivers/cpufreq/amd-pstate.c | 21 ++---------------
2 files changed, 39 insertions(+), 26 deletions(-)
--
2.43.0
Powered by blists - more mailing lists