From: "Limonciello, Mario" <Mario.Limonciello@amd.com>
To: shouyeliu <shouyeliu@gmail.com>, "Huang, Ray" <Ray.Huang@amd.com>,
"Shenoy, Gautham Ranjal" <gautham.shenoy@amd.com>,
"Yuan, Perry" <Perry.Yuan@amd.com>,
"corbet@lwn.net" <corbet@lwn.net>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Shouye Liu <shouyeliu@tencent.com>
Subject: Re: [PATCH] Documentation: amd-pstate:fix minimum performance state label error
Date: Thu, 22 May 2025 17:35:20 +0000 [thread overview]
Message-ID: <d1281f23-69c6-4386-9d26-6f2cd95343cc@amd.com> (raw)
In-Reply-To: <20250522070140.17557-1-shouyeliu@gmail.com>
On 5/22/25 2:01 AM, shouyeliu wrote:
> In the AMD P-States Performance Scale diagram, the labels for "Max Perf"
> and "Lowest Perf" were incorrectly used to define the range for
> "Desired Perf".The "Desired performance target" should be bounded by the
> "Maximum requested performance" and the "Minimum requested performance",
> which corresponds to "Max Perf" and "Min Perf", respectively.
>
> Signed-off-by: Shouye Liu <shouyeliu@tencent.com>
> ---
> Documentation/admin-guide/pm/amd-pstate.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/pm/amd-pstate.rst b/Documentation/admin-guide/pm/amd-pstate.rst
> index 412423c54f25..e1771f2225d5 100644
> --- a/Documentation/admin-guide/pm/amd-pstate.rst
> +++ b/Documentation/admin-guide/pm/amd-pstate.rst
> @@ -72,7 +72,7 @@ to manage each performance update behavior. ::
> Lowest non- | | | |
> linear perf ------>+-----------------------+ +-----------------------+
> | | | |
> - | | Lowest perf ---->| |
> + | | Min perf ---->| |
> | | | |
> Lowest perf ------>+-----------------------+ +-----------------------+
> | | | |
Makes sense to me. Thanks.
Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
next prev parent reply other threads:[~2025-05-22 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 7:01 shouyeliu
2025-05-22 17:35 ` Limonciello, Mario [this message]
2025-06-09 21:15 ` Jonathan Corbet
2025-06-19 19:24 linux-next: Signed-off-by missing for commit in the jc_docs tree Jonathan Corbet
2025-06-20 2:16 ` [PATCH] Documentation: amd-pstate:fix minimum performance state label error shouyeliu
2025-06-21 20:11 ` Jonathan Corbet
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=d1281f23-69c6-4386-9d26-6f2cd95343cc@amd.com \
--to=mario.limonciello@amd.com \
--cc=Perry.Yuan@amd.com \
--cc=Ray.Huang@amd.com \
--cc=corbet@lwn.net \
--cc=gautham.shenoy@amd.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=shouyeliu@gmail.com \
--cc=shouyeliu@tencent.com \
/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®