From: Peter Zijlstra <peterz@infradead.org>
To: Meng Li <li.meng@amd.com>
Cc: "Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Huang Rui <ray.huang@amd.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, linux-acpi@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kselftest@vger.kernel.org,
Nathan Fontenot <nathan.fontenot@amd.com>,
Deepak Sharma <deepak.sharma@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Shimmer Huang <shimmer.huang@amd.com>,
Perry Yuan <Perry.Yuan@amd.com>,
Xiaojian Du <Xiaojian.Du@amd.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH V1 3/6] cpufreq: Add a notification message that the highest perf has changed
Date: Tue, 8 Aug 2023 11:12:24 +0200 [thread overview]
Message-ID: <20230808091224.GW212435@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230808081001.2215240-4-li.meng@amd.com>
On Tue, Aug 08, 2023 at 04:09:58PM +0800, Meng Li wrote:
> Please refer to the ACPI_Spec for details on the highest
> performance and notify events of CPPC.
Please summarise so that we don't get to click random links on the
interweb just to try and make sense of things.
> Signed-off-by: Meng Li <li.meng@amd.com>
> Link: https://uefi.org/htmlspecs/AddCPI_Spec_6_4_html/08_Processor_Configuration_and_Control/declaring-processors.html?highlight=0x85#highest-performance
> ---
> drivers/acpi/processor_driver.c | 6 ++++++
> drivers/cpufreq/cpufreq.c | 13 +++++++++++++
> include/linux/cpufreq.h | 4 ++++
> 3 files changed, 23 insertions(+)
>
> diff --git a/drivers/acpi/processor_driver.c b/drivers/acpi/processor_driver.c
> index 4bd16b3f0781..29b2fb68a35d 100644
> --- a/drivers/acpi/processor_driver.c
> +++ b/drivers/acpi/processor_driver.c
> @@ -27,6 +27,7 @@
> #define ACPI_PROCESSOR_NOTIFY_PERFORMANCE 0x80
> #define ACPI_PROCESSOR_NOTIFY_POWER 0x81
> #define ACPI_PROCESSOR_NOTIFY_THROTTLING 0x82
> +#define ACPI_PROCESSOR_NOTIFY_HIGEST_PERF_CHANGED 0x85
Isn't that spelled: 'highest' ?
^
next prev parent reply other threads:[~2023-08-08 17:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 8:09 [PATCH V1 0/6] AMD Pstate Preferred Core Meng Li
2023-08-08 8:09 ` [PATCH V1 1/6] ACPI: CPPC: Add get the highest performance cppc control Meng Li
2023-08-08 15:43 ` Mario Limonciello
2023-08-08 8:09 ` [PATCH V1 2/6] cpufreq: amd-pstate: Enable AMD Pstate Preferred Core Supporting Meng Li
2023-08-08 9:06 ` Peter Zijlstra
2023-08-08 15:28 ` Mario Limonciello
2023-08-08 15:35 ` Mario Limonciello
2023-08-08 8:09 ` [PATCH V1 3/6] cpufreq: Add a notification message that the highest perf has changed Meng Li
2023-08-08 9:12 ` Peter Zijlstra [this message]
2023-08-08 8:09 ` [PATCH V1 4/6] cpufreq: amd-pstate: Update AMD Pstate Preferred Core ranking dynamically Meng Li
2023-08-08 8:10 ` [PATCH V1 5/6] Documentation: amd-pstate: introduce AMD Pstate Preferred Core Meng Li
2023-08-08 15:40 ` Mario Limonciello
2023-08-08 8:10 ` [PATCH V1 6/6] Documentation: introduce AMD Pstate Preferrd Core mode kernel command line options Meng Li
2023-08-08 15:37 ` Mario Limonciello
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230808091224.GW212435@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Perry.Yuan@amd.com \
--cc=Xiaojian.Du@amd.com \
--cc=alexander.deucher@amd.com \
--cc=bp@alien8.de \
--cc=deepak.sharma@amd.com \
--cc=li.meng@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=nathan.fontenot@amd.com \
--cc=rafael.j.wysocki@intel.com \
--cc=ray.huang@amd.com \
--cc=shimmer.huang@amd.com \
--cc=skhan@linuxfoundation.org \
--cc=viresh.kumar@linaro.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox