From: Richael Zhuang <Richael.Zhuang@arm.com>
To: David Hunt <david.hunt@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "yux.jiang@intel.com" <yux.jiang@intel.com>, nd <nd@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v4 1/2] power: add support for cppc cpufreq
Date: Thu, 24 Jun 2021 02:13:31 +0000 [thread overview]
Message-ID: <AM8PR08MB57966CDC2624C0D9AD5DCA5C92079@AM8PR08MB5796.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <3b4ea392-5fd6-eba8-e566-4ae3db2b140f@intel.com>
> -----Original Message-----
> From: David Hunt <david.hunt@intel.com>
> Sent: Wednesday, June 23, 2021 10:10 PM
> To: Richael Zhuang <Richael.Zhuang@arm.com>; dev@dpdk.org
> Cc: yux.jiang@intel.com
> Subject: Re: [PATCH v4 1/2] power: add support for cppc cpufreq
>
> Hi Richael
>
> On 23/6/2021 4:55 AM, Richael Zhuang wrote:
> > Currently in DPDK only acpi_cpufreq and pstate_cpufreq drivers are
> > supported, which are both not available on arm64 platforms. Add
> > support for cppc_cpufreq driver which works on most arm64 platforms.
> >
> > Signed-off-by: Richael Zhuang <richael.zhuang@arm.com>
> > ---
> > app/test/test_power.c | 3 +-
> > app/test/test_power_cpufreq.c | 3 +-
> > lib/power/meson.build | 1 +
> > lib/power/power_cppc_cpufreq.c | 632
> +++++++++++++++++++++++++++++++++
> > lib/power/power_cppc_cpufreq.h | 229 ++++++++++++
> > lib/power/rte_power.c | 26 ++
> > lib/power/rte_power.h | 2 +-
> > 7 files changed, 893 insertions(+), 3 deletions(-)
> > create mode 100644 lib/power/power_cppc_cpufreq.c
> > create mode 100644 lib/power/power_cppc_cpufreq.h
> >
> > diff --git a/app/test/test_power.c b/app/test/test_power.c index
> > da1d67c0a..b7b556134 100644
> > --- a/app/test/test_power.c
> > +++ b/app/test/test_power.c
> > @@ -133,7 +133,8 @@ test_power(void)
> > /* Perform tests for valid environments.*/
> > const enum power_management_env envs[] =
> {PM_ENV_ACPI_CPUFREQ,
> > PM_ENV_KVM_VM,
> > - PM_ENV_PSTATE_CPUFREQ};
> > + PM_ENV_PSTATE_CPUFREQ,
> > + PM_ENV_CPPC_CPUFREQ};
> >
> > unsigned int i;
> > for (i = 0; i < RTE_DIM(envs); ++i) { diff --git
> > a/app/test/test_power_cpufreq.c b/app/test/test_power_cpufreq.c index
> > 0c3adc5f3..8516df4ca 100644
> > --- a/app/test/test_power_cpufreq.c
> > +++ b/app/test/test_power_cpufreq.c
> > @@ -496,7 +496,8 @@ test_power_cpufreq(void)
> >
> > /* Test environment configuration */
> > env = rte_power_get_env();
> > - if ((env != PM_ENV_ACPI_CPUFREQ) && (env !=
> PM_ENV_PSTATE_CPUFREQ)) {
> > + if ((env != PM_ENV_ACPI_CPUFREQ) && (env !=
> PM_ENV_PSTATE_CPUFREQ) &&
> > + (env != PM_ENV_CPPC_CPUFREQ)) {
> > printf("Unexpectedly got an environment other than
> ACPI/PSTATE\n");
> > goto fail_all;
> > }
> > diff --git a/lib/power/meson.build b/lib/power/meson.build index
> > 74c5f3a29..4a5b07292 100644
> > --- a/lib/power/meson.build
> > +++ b/lib/power/meson.build
> > @@ -21,6 +21,7 @@ sources = files(
> > 'rte_power.c',
> > 'rte_power_empty_poll.c',
> > 'rte_power_pmd_mgmt.c',
> > + 'power_cppc_cpufreq.c',
> > )
> > headers = files(
> > 'rte_power.h',
> > diff --git a/lib/power/power_cppc_cpufreq.c
> > b/lib/power/power_cppc_cpufreq.c new file mode 100644 index
> > 000000000..fd4483e52
> > --- /dev/null
> > +++ b/lib/power/power_cppc_cpufreq.c
> > @@ -0,0 +1,632 @@
> > +/* SPDX-License-Identifier: BSD-3-Clause
> > + * Copyright(c) 2021 Arm Limited
>
>
> Since this is a port of the acpi or p-state code for the cppc driver, I think you
> need to keep the Intel line in there, and then add in the Arm Line. Suggest
> adding in:
>
> * Copyright(c) 2010-2021 Intel Corporation
>
>
> Also, (I know you're looking at this already), the FOPS* and FOPEN* macros
> need to be removed to bring in line with the latest (v6) patch for the cleanup
> work, a few people have been wanting to remove those macros for a while
> now :)
>
Hi David,
Thanks! I will submit a new version soon.
> Once that's done, this patch looks good to me, although I can't give it a run as
> I don't have access to a suitable system. But visually, I've read through the
> patch and it seems fine to me.
>
> Reviewed-by: David Hunt <david.hunt@intel.com>
>
>
> --snip--
next prev parent reply other threads:[~2021-06-24 2:13 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 6:15 [dpdk-dev] [PATCH v1 0/1] power: add support for cppc cpufreq driver Richael Zhuang
2021-04-22 6:15 ` [dpdk-dev] [PATCH v1 1/1] power: add support for cppc cpufreq Richael Zhuang
2021-04-22 9:06 ` Burakov, Anatoly
2021-04-22 9:29 ` Richael Zhuang
2021-04-22 9:59 ` Burakov, Anatoly
2021-04-22 10:02 ` Richael Zhuang
2021-04-23 11:37 ` Burakov, Anatoly
2021-04-24 7:03 ` Richael Zhuang
2021-05-12 3:49 ` [dpdk-dev] [PATCH v2 0/2] power: add support for cppc cpufreq driver Richael Zhuang
2021-05-12 3:49 ` [dpdk-dev] [PATCH v2 1/2] power: add support for cppc cpufreq Richael Zhuang
2021-05-12 3:49 ` [dpdk-dev] [PATCH v2 2/2] test/power: round cpuinfo cur freq only when using CPPC cpufreq Richael Zhuang
2021-05-12 3:57 ` [dpdk-dev] [PATCH v3 0/2] power: add support for cppc cpufreq driver Richael Zhuang
2021-05-12 3:57 ` [dpdk-dev] [PATCH v3 1/2] power: add support for cppc cpufreq Richael Zhuang
2021-06-23 3:55 ` [dpdk-dev] [PATCH v4 0/2] power: add support for cppc cpufreq driver Richael Zhuang
2021-06-23 3:55 ` [dpdk-dev] [PATCH v4 1/2] power: add support for cppc cpufreq Richael Zhuang
2021-06-23 14:10 ` David Hunt
2021-06-24 2:13 ` Richael Zhuang [this message]
2021-06-25 2:02 ` [dpdk-dev] [PATCH v5 0/2] power: add support for cppc cpufreq driver Richael Zhuang
2021-06-25 2:02 ` [dpdk-dev] [PATCH v5 1/2] power: add support for cppc cpufreq Richael Zhuang
2021-07-07 13:47 ` David Hunt
2021-07-08 2:09 ` Richael Zhuang
2021-07-08 2:34 ` [dpdk-dev] [PATCH v6 0/2] power: add support for cppc cpufreq driver Richael Zhuang
2021-07-08 2:34 ` [dpdk-dev] [PATCH v6 1/2] power: add support for cppc cpufreq Richael Zhuang
2021-07-08 8:27 ` David Hunt
2021-07-08 13:30 ` David Marchand
2021-07-08 20:43 ` David Marchand
2021-07-09 2:37 ` Richael Zhuang
2021-07-09 3:34 ` [dpdk-dev] [PATCH v7 0/2] power: add support for cppc cpufreq driver Richael Zhuang
2021-07-09 3:34 ` [dpdk-dev] [PATCH v7 1/2] power: add support for cppc cpufreq Richael Zhuang
2021-07-09 9:10 ` David Marchand
2021-07-09 10:35 ` Richael Zhuang
2021-07-09 9:52 ` David Hunt
2021-07-09 10:55 ` [dpdk-dev] [PATCH v8 0/2] power: add support for cppc cpufreq driver Richael Zhuang
2021-07-09 10:55 ` [dpdk-dev] [PATCH v8 1/2] power: add support for cppc cpufreq Richael Zhuang
2021-07-09 10:55 ` [dpdk-dev] [PATCH v8 2/2] test/power: round cpuinfo cur freq only in CPPC cpufreq Richael Zhuang
2021-07-09 14:07 ` [dpdk-dev] [PATCH v8 0/2] power: add support for cppc cpufreq driver David Marchand
2021-07-12 2:05 ` Richael Zhuang
2021-07-09 3:34 ` [dpdk-dev] [PATCH v7 2/2] test/power: round cpuinfo cur freq only in CPPC cpufreq Richael Zhuang
2021-07-08 2:34 ` [dpdk-dev] [PATCH v6 " Richael Zhuang
2021-07-08 8:27 ` David Hunt
2021-06-25 2:02 ` [dpdk-dev] [PATCH v5 2/2] test/power: round cpuinfo cur freq only when using " Richael Zhuang
2021-06-23 3:55 ` [dpdk-dev] [PATCH v4 " Richael Zhuang
2021-06-23 14:13 ` David Hunt
2021-05-12 3:57 ` [dpdk-dev] [PATCH v3 " Richael Zhuang
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=AM8PR08MB57966CDC2624C0D9AD5DCA5C92079@AM8PR08MB5796.eurprd08.prod.outlook.com \
--to=richael.zhuang@arm.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=yux.jiang@intel.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;
as well as URLs for NNTP newsgroup(s).