From: Huang Rui <ray.huang@amd.com>
To: Erwan Velu <erwanaliasr1@gmail.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Erwan Velu <e.velu@criteo.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] cpufreq/amd-pstate: Adding Zen4 support in introduction
Date: Thu, 11 Jan 2024 11:25:18 +0800 [thread overview]
Message-ID: <ZZ9fntJX4bTDK46b@amd.com> (raw)
In-Reply-To: <CAL2Jzuzq-HVnhGZ8W0bSH6xibpYWXdXc30kC1Ub4vESfc4w7xA@mail.gmail.com>
On Thu, Jan 11, 2024 at 01:49:27AM +0800, Erwan Velu wrote:
> > How about modifying here as "partial Zen2, Zen3, and future processors"?
> And all processors starting Zen4 ?
"partial Zen2 and all processors starting Zen3"
Thanks,
Ray
>
> Le mer. 10 janv. 2024 à 18:19, Huang Rui <ray.huang@amd.com> a écrit :
> >
> > On Wed, Jan 10, 2024 at 10:21:20PM +0800, Rafael J. Wysocki wrote:
> > > On Tue, Jan 9, 2024 at 6:58 PM Erwan Velu <erwanaliasr1@gmail.com> wrote:
> > > >
> > > > amd-pstate is implemented on Zen4, adding this architecture in the
> > > > introduction.
> > > >
> > > > Signed-off-by: Erwan Velu <e.velu@criteo.com>
> > > > ---
> > > > drivers/cpufreq/amd-pstate.c | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c
> > > > index 1f6186475715..9a8d083f6ba5 100644
> > > > --- a/drivers/cpufreq/amd-pstate.c
> > > > +++ b/drivers/cpufreq/amd-pstate.c
> > > > @@ -14,7 +14,7 @@
> > > > * communicate the performance hints to hardware.
> > > > *
> > > > * AMD P-State is supported on recent AMD Zen base CPU series include some of
> > > > - * Zen2 and Zen3 processors. _CPC needs to be present in the ACPI tables of AMD
> > > > + * Zen2, Zen3 and Zen4 processors. _CPC needs to be present in the ACPI tables of AMD
> > >
> > > IMO, it would be really nice to avoid extending this line so much, but
> > > this is up to the AMD people.
> >
> > Agree. Actually, we will use this driver for all future AMD CPU generations
> > that starts from paritial Zen2.
> >
> > >
> > > Also, while you are at it, "include" in the first sentence should be
> > > "including" and a new paragraph after "processors." would make this
> > > comment easier to follow from the logical standpoint, because the
> > > first sentence is about the supported platforms and the second one is
> > > about additional requirements (ie. something else).
> > >
> >
> > How about modifying here as "partial Zen2, Zen3, and future processors"?
> >
> > Thanks,
> > Ray
> >
> > > > * P-State supported system. And there are two types of hardware implementations
> > > > * for AMD P-State: 1) Full MSR Solution and 2) Shared Memory Solution.
> > > > * X86_FEATURE_CPPC CPU feature flag is used to distinguish the different types.
> > > > --
prev parent reply other threads:[~2024-01-11 3:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 17:58 [PATCH 2/2] cpufreq/amd-pstate: Adding Zen4 support in introduction Erwan Velu
2024-01-10 14:21 ` Rafael J. Wysocki
2024-01-10 14:30 ` Erwan Velu
2024-01-10 17:19 ` Huang Rui
2024-01-10 17:49 ` Erwan Velu
2024-01-11 3:25 ` 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=ZZ9fntJX4bTDK46b@amd.com \
--to=ray.huang@amd.com \
--cc=e.velu@criteo.com \
--cc=erwanaliasr1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.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