From: "Tummala, Sivaprasad" <Sivaprasad.Tummala@amd.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "david.hunt@intel.com" <david.hunt@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Yigit, Ferruh" <Ferruh.Yigit@amd.com>,
"anatoly.burakov@intel.com" <anatoly.burakov@intel.com>,
"Laatz, Kevin" <kevin.laatz@intel.com>
Subject: RE: [PATCH v1] power: support amd-pstate cpufreq driver
Date: Tue, 30 May 2023 10:45:56 +0000 [thread overview]
Message-ID: <BL1PR12MB5777FCEF634D6876317D5EDF864B9@BL1PR12MB5777.namprd12.prod.outlook.com> (raw)
In-Reply-To: <3000723.687JKscXgg@thomas>
[AMD Official Use Only - General]
Hi Thomas,
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Thursday, May 25, 2023 12:17 AM
> To: Tummala, Sivaprasad <Sivaprasad.Tummala@amd.com>
> Cc: david.hunt@intel.com; dev@dpdk.org; Yigit, Ferruh <Ferruh.Yigit@amd.com>;
> anatoly.burakov@intel.com; Laatz, Kevin <kevin.laatz@intel.com>
> Subject: Re: [PATCH v1] power: support amd-pstate cpufreq driver
>
> Caution: This message originated from an External Source. Use proper caution
> when opening attachments, clicking links, or responding.
>
>
> 12/04/2023 11:52, Sivaprasad Tummala:
> > amd-pstate introduces a new CPU frequency control mechanism for AMD
> > processors using the ACPI Collaborative Performance Power Control
> > feature for a finer grained frequency management.
> >
> > Patch to add support for amd-pstate driver.
> >
> > Signed-off-by: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
> > ---
> > app/test/test_power.c | 1 +
> > app/test/test_power_cpufreq.c | 5 +-
> > doc/guides/rel_notes/release_23_07.rst | 3 +
> > examples/l3fwd-power/main.c | 1 +
> > lib/power/meson.build | 1 +
> > lib/power/power_amd_pstate_cpufreq.c | 698
> +++++++++++++++++++++++++
> > lib/power/power_amd_pstate_cpufreq.h | 219 ++++++++
> > lib/power/rte_power.c | 26 +
> > lib/power/rte_power.h | 3 +-
> > lib/power/rte_power_pmd_mgmt.c | 6 +-
> > 10 files changed, 958 insertions(+), 5 deletions(-)
>
> I'm not comfortable to merge this patch without a word from David Hunt.
> Given there is 0 review, what do we do?
Yes, we are waiting for feedback from the community on this patch.
>
>
> > Also, make sure to start the actual text at the margin.
> >
> ====================================================
> ===
> >
> > + * **Added amd-pstate driver support to power management library.**
> > +
> > + Added support for amd-pstate driver which works on AMD Zen processors.
>
> Looks like the indent is not correct.
Sure, will fix it in v2 patch
>
> > 'power_pstate_cpufreq.c',
> > + 'power_amd_pstate_cpufreq.c',
>
> Can you say briefly why AMD has a different pstate?
> Does it mean power_pstate_cpufreq.c should be renamed
> power_intel_pstate_cpufreq.c?
amd-pstate is the new AMD CPU performance scaling driver based on CPPC.
It is implemented as a new kernel driver and we need a different library from
Power_pstate_cpufreq. Yes, it makes sense to rename this, inline with the
Linux kernel as indicated below.
linux/latest/source/drivers/cpufreq
- amd-pstate.c
- cppc_cpufreq.c
- intel_pstate.c
>
> > +++ b/lib/power/power_amd_pstate_cpufreq.c
> > @@ -0,0 +1,698 @@
> > +/* SPDX-License-Identifier: BSD-3-Clause
> > + * Copyright(c) 2010-2021 Intel Corporation
> > + * Copyright(c) 2021 Arm Limited
>
> Why is there copyright for Intel and Arm?
> Does it mean you copied some code and did not try to keep common code in a
> common place?
Yes, few internal functions follow similar notion as power_cppc_cpufreq.c
>
> > + * Copyright(c) 2023 Amd Limited
>
>
Thanks & Regards,
Sivaprasad
next prev parent reply other threads:[~2023-05-30 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 9:52 Sivaprasad Tummala
2023-05-24 18:46 ` Thomas Monjalon
2023-05-26 16:51 ` Burakov, Anatoly
2023-05-30 10:45 ` Tummala, Sivaprasad [this message]
2023-05-26 16:54 ` Burakov, Anatoly
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=BL1PR12MB5777FCEF634D6876317D5EDF864B9@BL1PR12MB5777.namprd12.prod.outlook.com \
--to=sivaprasad.tummala@amd.com \
--cc=Ferruh.Yigit@amd.com \
--cc=anatoly.burakov@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=kevin.laatz@intel.com \
--cc=thomas@monjalon.net \
/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).