From: Thomas Monjalon <thomas@monjalon.net>
To: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Cc: david.hunt@intel.com, dev@dpdk.org, ferruh.yigit@amd.com,
anatoly.burakov@intel.com, "Laatz, Kevin" <kevin.laatz@intel.com>
Subject: Re: [PATCH v1] power: support amd-pstate cpufreq driver
Date: Wed, 24 May 2023 20:46:59 +0200 [thread overview]
Message-ID: <3000723.687JKscXgg@thomas> (raw)
In-Reply-To: <20230412095244.967182-1-Sivaprasad.Tummala@amd.com>
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?
> 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.
> '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?
> +++ 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?
> + * Copyright(c) 2023 Amd Limited
next prev parent reply other threads:[~2023-05-24 18:47 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 [this message]
2023-05-26 16:51 ` Burakov, Anatoly
2023-05-30 10:45 ` Tummala, Sivaprasad
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=3000723.687JKscXgg@thomas \
--to=thomas@monjalon.net \
--cc=Sivaprasad.Tummala@amd.com \
--cc=anatoly.burakov@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=kevin.laatz@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).