Re: [PATCH 1/2] x86/cpu/amd: Clarify amd_get_highest_perf()

From: Borislav Petkov
Date: Wed Jun 26 2024 - 23:01:06 EST

Next message: zhouquan: "[PATCH v1 0/2] riscv: Expose orig_a0 to userspace for ptrace to set the actual a0"
Previous message: syzbot: "Re: [syzbot] Re: [syzbot] [jfs?] INFO: task hung in txBegin"
In reply to: Mario Limonciello: "Re: [PATCH 1/2] x86/cpu/amd: Clarify amd_get_highest_perf()"
Next in thread: Mario Limonciello: "[PATCH 2/2] cpufreq: amd-pstate: Use amd_get_highest_perf() to lookup perf values"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, Jun 26, 2024 at 01:18:17PM -0500, Mario Limonciello wrote:
> And then patch 2 or patch 3 change the "default" return to 166 and if there
> is functional issues then they need to be special cased.

Sounds ok to me. Keep the whole logic in one place. Sure.

--
Regards/Gruss,
Boris.

https://people.kernel.org/tglx/notes-about-netiquette

Next message: zhouquan: "[PATCH v1 0/2] riscv: Expose orig_a0 to userspace for ptrace to set the actual a0"
Previous message: syzbot: "Re: [syzbot] Re: [syzbot] [jfs?] INFO: task hung in txBegin"
In reply to: Mario Limonciello: "Re: [PATCH 1/2] x86/cpu/amd: Clarify amd_get_highest_perf()"
Next in thread: Mario Limonciello: "[PATCH 2/2] cpufreq: amd-pstate: Use amd_get_highest_perf() to lookup perf values"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]