public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Meng Li <li.meng@amd.com>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	Huang Rui <ray.huang@amd.com>
Cc: 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>,
	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 V2 4/7] cpufreq: Add a notification message that the highest perf has changed
Date: Tue, 15 Aug 2023 10:28:06 -0500	[thread overview]
Message-ID: <343e5729-cc88-4ec8-b166-3b33a8ca989e@amd.com> (raw)
In-Reply-To: <20230815061546.3556083-5-li.meng@amd.com>

On 8/15/2023 01:15, Meng Li wrote:
> Please refer to the ACPI_Spec for details on the highest
> performance and notify events of CPPC.

I would suggest wording this differently. Maybe something like:

ACPI 6.5 section 8.4.6.1.1.1 specifies that Notify event 0x85 can be
emitted to cause the the OSPM to re-evaluate the highest performance
register.  Add support for this event.

> 
> Signed-off-by: Meng Li <li.meng@amd.com>
> Link: https://uefi.org/specs/ACPI/6.5/08_Processor_Configuration_and_Control.html?highlight=cppc#cpc-continuous-performance-control
> ---
>   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
>   
>   MODULE_AUTHOR("Paul Diefenbaugh");
>   MODULE_DESCRIPTION("ACPI Processor Driver");
> @@ -83,6 +84,11 @@ static void acpi_processor_notify(acpi_handle handle, u32 event, void *data)
>   		acpi_bus_generate_netlink_event(device->pnp.device_class,
>   						  dev_name(&device->dev), event, 0);
>   		break;
> +	case ACPI_PROCESSOR_NOTIFY_HIGEST_PERF_CHANGED:
> +		cpufreq_update_highest_perf(pr->id);
> +		acpi_bus_generate_netlink_event(device->pnp.device_class,
> +						  dev_name(&device->dev), event, 0);
> +		break;
>   	default:
>   		acpi_handle_debug(handle, "Unsupported event [0x%x]\n", event);
>   		break;
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> index 50bbc969ffe5..842357abfae6 100644
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -2675,6 +2675,19 @@ void cpufreq_update_limits(unsigned int cpu)
>   }
>   EXPORT_SYMBOL_GPL(cpufreq_update_limits);
>   
> +/**
> + * cpufreq_update_highest_perf - Update highest performance for a given CPU.
> + * @cpu: CPU to update the highest performance for.
> + *
> + * Invoke the driver's ->update_highest_perf callback if present
> + */
> +void cpufreq_update_highest_perf(unsigned int cpu)
> +{
> +	if (cpufreq_driver->update_highest_perf)
> +		cpufreq_driver->update_highest_perf(cpu);
> +}
> +EXPORT_SYMBOL_GPL(cpufreq_update_highest_perf);
> +
>   /*********************************************************************
>    *               BOOST						     *
>    *********************************************************************/
> diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
> index 172ff51c1b2a..766c83a4fae7 100644
> --- a/include/linux/cpufreq.h
> +++ b/include/linux/cpufreq.h
> @@ -231,6 +231,7 @@ int cpufreq_get_policy(struct cpufreq_policy *policy, unsigned int cpu);
>   void refresh_frequency_limits(struct cpufreq_policy *policy);
>   void cpufreq_update_policy(unsigned int cpu);
>   void cpufreq_update_limits(unsigned int cpu);
> +void cpufreq_update_highest_perf(unsigned int cpu);
>   bool have_governor_per_policy(void);
>   bool cpufreq_supports_freq_invariance(void);
>   struct kobject *get_governor_parent_kobj(struct cpufreq_policy *policy);
> @@ -376,6 +377,9 @@ struct cpufreq_driver {
>   	/* Called to update policy limits on firmware notifications. */
>   	void		(*update_limits)(unsigned int cpu);
>   
> +	/* Called to update highest performance on firmware notifications. */
> +	void		(*update_highest_perf)(unsigned int cpu);
> +
>   	/* optional */
>   	int		(*bios_limit)(int cpu, unsigned int *limit);
>   


  reply	other threads:[~2023-08-15 15:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15  6:15 [PATCH V2 0/7] AMD Pstate Preferred Core Meng Li
2023-08-15  6:15 ` [PATCH V2 1/7] x86: Drop CPU_SUP_INTEL from SCHED_MC_PRIO for the expansion Meng Li
2023-08-15 15:20   ` Mario Limonciello
2023-08-15  6:15 ` [PATCH V2 2/7] acpi: cppc: Add get the highest performance cppc control Meng Li
2023-08-15  6:15 ` [PATCH V2 3/7] cpufreq: amd-pstate: Enable AMD Pstate Preferred Core Supporting Meng Li
2023-08-15 15:23   ` Mario Limonciello
2023-08-15  6:15 ` [PATCH V2 4/7] cpufreq: Add a notification message that the highest perf has changed Meng Li
2023-08-15 15:28   ` Mario Limonciello [this message]
2023-08-15  6:15 ` [PATCH V2 5/7] cpufreq: amd-pstate: Update AMD Pstate Preferred Core ranking dynamically Meng Li
2023-08-15  6:15 ` [PATCH V2 6/7] Documentation: amd-pstate: introduce AMD Pstate Preferred Core Meng Li
2023-08-15 15:34   ` Mario Limonciello
2023-08-15  6:15 ` [PATCH V2 7/7] Documentation: introduce AMD Pstate Preferrd Core mode kernel command line options Meng Li
2023-08-15 15:34   ` 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=343e5729-cc88-4ec8-b166-3b33a8ca989e@amd.com \
    --to=mario.limonciello@amd.com \
    --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=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