dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>, <david.hunt@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v1] power: support amd-pstate cpufreq driver
Date: Fri, 26 May 2023 17:54:05 +0100	[thread overview]
Message-ID: <1df9c419-623b-d922-e3cc-019c8cc751ba@intel.com> (raw)
In-Reply-To: <20230412095244.967182-1-Sivaprasad.Tummala@amd.com>

On 4/12/2023 10:52 AM, Sivaprasad Tummala wrote:
> 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>
> ---

I don't have an AMD machine handy so I can't test this, but code wise, 
LGTM bar one nitpick below.

Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>

> +	}
> +
> +	ret = read_core_sysfs_u32(f_nom, &nominal_freq);
> +	if (ret < 0) {
> +		RTE_LOG(ERR, POWER, "Failed to read %s\n",
> +				POWER_SYSFILE_NOMINAL_FREQ);
> +		goto out;
> +	}
> +
> +	power_check_turbo(pi);
> +
> +	if (scaling_max_freq < scaling_min_freq)

It would be nice if this produced an error message of some kind.

-- 
Thanks,
Anatoly


      parent reply	other threads:[~2023-05-26 16:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12  9:52 [PATCH v1] power: support amd-pstate cpufreq driver Sivaprasad Tummala
2023-05-24 18:46 ` Thomas Monjalon
2023-05-26 16:51   ` Burakov, Anatoly
2023-05-30 10:45   ` Tummala, Sivaprasad
2023-05-26 16:54 ` Burakov, Anatoly [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=1df9c419-623b-d922-e3cc-019c8cc751ba@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=Sivaprasad.Tummala@amd.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).