From: Huang Rui <ray.huang@amd.com>
To: "Karny, Wyes" <Wyes.Karny@amd.com>
Cc: Rafael J Wysocki <rafael@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
"Limonciello, Mario" <Mario.Limonciello@amd.com>,
"Yuan, Perry" <Perry.Yuan@amd.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
"Shukla, Santosh" <Santosh.Shukla@amd.com>,
Len Brown <lenb@kernel.org>,
Robert Moore <robert.moore@intel.com>,
Borislav Petkov <bp@alien8.de>,
"Narayan, Ananth" <Ananth.Narayan@amd.com>,
"Shenoy, Gautham Ranjal" <gautham.shenoy@amd.com>,
Tor Vic <torvic9@mailbox.org>
Subject: Re: [PATCH v6 6/6] Documentation: amd_pstate: Update amd_pstate status sysfs for guided
Date: Thu, 16 Feb 2023 14:17:16 +0800 [thread overview]
Message-ID: <Y+3KbMV5u2GUPnUe@amd.com> (raw)
In-Reply-To: <20230206172157.49887-7-wyes.karny@amd.com>
On Tue, Feb 07, 2023 at 01:21:57AM +0800, Karny, Wyes wrote:
> Update amd_pstate status sysfs for guided mode.
>
> Signed-off-by: Wyes Karny <wyes.karny@amd.com>
> Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
> Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
Acked-by: Huang Rui <ray.huang@amd.com>
> ---
> Documentation/admin-guide/pm/amd-pstate.rst | 31 ++++++++++++++++-----
> 1 file changed, 24 insertions(+), 7 deletions(-)
>
> diff --git a/Documentation/admin-guide/pm/amd-pstate.rst b/Documentation/admin-guide/pm/amd-pstate.rst
> index 5304adf2fc2f..95d2d0a803fe 100644
> --- a/Documentation/admin-guide/pm/amd-pstate.rst
> +++ b/Documentation/admin-guide/pm/amd-pstate.rst
> @@ -303,13 +303,18 @@ efficiency frequency management method on AMD processors.
> AMD Pstate Driver Operation Modes
> =================================
>
> -``amd_pstate`` CPPC has two operation modes: CPPC Autonomous(active) mode and
> -CPPC non-autonomous(passive) mode.
> -active mode and passive mode can be chosen by different kernel parameters.
> -When in Autonomous mode, CPPC ignores requests done in the Desired Performance
> -Target register and takes into account only the values set to the Minimum requested
> -performance, Maximum requested performance, and Energy Performance Preference
> -registers. When Autonomous is disabled, it only considers the Desired Performance Target.
> +``amd_pstate`` CPPC has 3 operation modes: autonomous (active) mode,
> +non-autonomous (passive) mode and guided autonomous (guided) mode.
> +Active/passive/guided mode can be chosen by different kernel parameters.
> +
> +- In autonomous mode, platform ignores the desired performance level request
> + and takes into account only the values set to the minimum, maximum and energy
> + performance preference registers.
> +- In non-autonomous mode, platform gets desired performance level
> + from OS directly through Desired Performance Register.
> +- In guided-autonomous mode, platform sets operating performance level
> + autonomously according to the current workload and within the limits set by
> + OS through min and max performance registers.
>
> Active Mode
> ------------
> @@ -338,6 +343,15 @@ to the Performance Reduction Tolerance register. Above the nominal performance l
> processor must provide at least nominal performance requested and go higher if current
> operating conditions allow.
>
> +Guided Mode
> +-----------
> +
> +``amd_pstate=guided``
> +
> +If ``amd_pstate=guided`` is passed to kernel command line option then this mode
> +is activated. In this mode, driver requests minimum and maximum performance
> +level and the platform autonomously selects a performance level in this range
> +and appropriate to the current workload.
>
> User Space Interface in ``sysfs``
> =================================
> @@ -358,6 +372,9 @@ control its functionality at the system level. They are located in the
> "passive"
> The driver is functional and in the ``passive mode``
>
> + "guided"
> + The driver is functional and in the ``guided mode``
> +
> "disable"
> The driver is unregistered and not functional now.
>
> --
> 2.34.1
>
prev parent reply other threads:[~2023-02-16 6:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 17:21 [PATCH v6 0/6] amd_pstate: Add guided autonomous mode support Wyes Karny
2023-02-06 17:21 ` [PATCH v6 1/6] acpi: cppc: Add min and max perf reg writing support Wyes Karny
2023-02-15 13:08 ` Huang Rui
2023-02-06 17:21 ` [PATCH v6 2/6] acpi: cppc: Add auto select register read/write support Wyes Karny
2023-02-15 14:16 ` Huang Rui
2023-02-06 17:21 ` [PATCH v6 3/6] cpufreq: amd_pstate: Add guided autonomous mode Wyes Karny
2023-02-16 6:08 ` Huang Rui
2023-02-16 6:42 ` Wyes Karny
2023-02-06 17:21 ` [PATCH v6 4/6] Documentation: amd_pstate: Move amd_pstate param to alphabetical order Wyes Karny
2023-02-16 6:12 ` Huang Rui
2023-02-16 6:33 ` Huang Rui
2023-02-16 6:44 ` Wyes Karny
2023-02-06 17:21 ` [PATCH v6 5/6] cpufreq: amd_pstate: Add guided mode control support via sysfs Wyes Karny
2023-02-16 6:15 ` Huang Rui
2023-02-06 17:21 ` [PATCH v6 6/6] Documentation: amd_pstate: Update amd_pstate status sysfs for guided Wyes Karny
2023-02-16 6:17 ` Huang Rui [this message]
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=Y+3KbMV5u2GUPnUe@amd.com \
--to=ray.huang@amd.com \
--cc=Ananth.Narayan@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Perry.Yuan@amd.com \
--cc=Santosh.Shukla@amd.com \
--cc=Wyes.Karny@amd.com \
--cc=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=gautham.shenoy@amd.com \
--cc=lenb@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=torvic9@mailbox.org \
--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;
as well as URLs for NNTP newsgroup(s).