From: Janakarajan Natarajan <jnataraj@amd.com>
To: "Natarajan, Janakarajan" <Janakarajan.Natarajan@amd.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"devel@acpica.org" <devel@acpica.org>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Robert Moore <robert.moore@intel.com>,
Erik Schmauss <erik.schmauss@intel.com>,
"Ghannam, Yazen" <Yazen.Ghannam@amd.com>
Subject: Re: [PATCH v2 0/7] CPPC optional registers AMD support
Date: Mon, 15 Apr 2019 22:35:48 +0000 [thread overview]
Message-ID: <d44f4893-0b67-4993-2942-6e03d29dffa1@amd.com> (raw)
In-Reply-To: <cover.1554410643.git.Janakarajan.Natarajan@amd.com>
On 4/4/19 4:25 PM, Natarajan, Janakarajan wrote:
> CPPC (Collaborative Processor Performance Control) offers optional
> registers which can be used to tune the system based on energy and/or
> performance requirements.
>
> Newer AMD processors add support for a subset of these optional CPPC
> registers, based on ACPI v6.1.
>
> The following are the supported CPPC registers for which sysfs entries
> are created:
> * enable (NEW)
> * max_perf (NEW)
> * min_perf (NEW)
> * energy_perf
> * lowest_perf
> * nominal_perf
> * desired_perf (NEW)
> * feedback_ctrs
> * auto_sel_enable (NEW)
> * lowest_nonlinear_perf
>
> The CPPC driver is updated to enable the OSPM and the userspace to
> access
> the newly supported registers.
>
> The purpose of exposing the registers via the sysfs entries is to allow
> the userspace to:
> * Tweak the values to fit its workload.
> * Apply a profile from AMD's optimization guides.
>
> Profiles will be documented in the performance/optimization guides.
>
> Note:
> * AMD systems will not have a policy applied in the kernel at this time.
> * By default, acpi_cpufreq will still be used.
>
> TODO:
> * Create a linux userspace tool that will help users generate a CPPC
> * profile
> for their target workload.
> * Create or update a driver to apply a general CPPC policy in the
> * kernel.
>
> v1->v2:
> * Add macro to ensure BUFFER only registers have BUFFER type.
> * Add support macro to make the right check based on register type.
> * Remove support checks for registers which are mandatory.
Are there any concerns regarding this patchset?
Thanks.
>
> Janakarajan Natarajan (2):
> acpi/cppc: Add macro for CPPC register BUFFER only check
> acpi/cppc: Ensure only supported CPPC sysfs entries are created
>
> Yazen Ghannam (5):
> acpi/cppc: Modify show_cppc_data macro
> acpi/cppc: Rework cppc_set_perf() to use cppc_regs index
> acpi/cppc: Add macros to define a R/W sysfs entry for CPPC registers
> acpi/cppc: Add support for optional CPPC registers
> acpi/cppc: Add support for CPPC Enable register
>
> drivers/acpi/cppc_acpi.c | 402 +++++++++++++++++++++++++++++----
> drivers/cpufreq/cppc_cpufreq.c | 6 +-
> include/acpi/cppc_acpi.h | 6 +-
> 3 files changed, 372 insertions(+), 42 deletions(-)
>
next prev parent reply other threads:[~2019-04-15 22:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 21:25 Natarajan, Janakarajan
2019-04-04 21:25 ` [PATCH v2 1/7] acpi/cppc: Add macro for CPPC register BUFFER only check Natarajan, Janakarajan
2019-04-04 21:25 ` [PATCH v2 2/7] acpi/cppc: Ensure only supported CPPC sysfs entries are created Natarajan, Janakarajan
2019-04-04 21:25 ` [PATCH v2 3/7] acpi/cppc: Modify show_cppc_data macro Natarajan, Janakarajan
2019-04-04 21:25 ` [PATCH v2 4/7] acpi/cppc: Rework cppc_set_perf() to use cppc_regs index Natarajan, Janakarajan
2019-04-04 21:25 ` [PATCH v2 5/7] acpi/cppc: Add macros to define a R/W sysfs entry for CPPC registers Natarajan, Janakarajan
2019-04-04 21:25 ` [PATCH v2 6/7] acpi/cppc: Add support for optional " Natarajan, Janakarajan
2019-04-04 21:25 ` [PATCH v2 7/7] acpi/cppc: Add support for CPPC Enable register Natarajan, Janakarajan
2019-04-15 22:35 ` Janakarajan Natarajan [this message]
2019-04-16 9:34 ` [PATCH v2 0/7] CPPC optional registers AMD support Rafael J. Wysocki
2019-04-17 17:28 ` Ghannam, Yazen
2019-04-17 22:10 ` Rafael J. Wysocki
2019-04-18 16:40 ` Ghannam, Yazen
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=d44f4893-0b67-4993-2942-6e03d29dffa1@amd.com \
--to=jnataraj@amd.com \
--cc=Janakarajan.Natarajan@amd.com \
--cc=Yazen.Ghannam@amd.com \
--cc=devel@acpica.org \
--cc=erik.schmauss@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.com \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®