From: David Marchand <david.marchand@redhat.com>
To: Richael Zhuang <richael.zhuang@arm.com>
Cc: David Hunt <david.hunt@intel.com>, dev <dev@dpdk.org>,
zhiminx.huang@intel.com, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 1/1] test/power: fix CPU frequency check
Date: Tue, 20 Jul 2021 17:20:18 +0200 [thread overview]
Message-ID: <CAJFAV8x6dyvRNOKQsxhJiwYE6WXH4BFpuuQFzfzqiBFFC2h04A@mail.gmail.com> (raw)
In-Reply-To: <10a8b0c7-af1d-2dfa-6c8d-d4764966a035@intel.com>
On Wed, Jul 14, 2021 at 2:23 PM David Hunt <david.hunt@intel.com> wrote:
> On 14/7/2021 11:44 AM, Richael Zhuang wrote:
> > For acpi_cpufreq and cppc_cpufreq, both cpuinfo_cur_freq and
> > scaling_cur_freq exist. For pstate, only scaling_cur_freq exists.
> > And value in scaling_cur_freq and cpuinfo_cur_freq may not be the
> > same. For acpi_cpufreq and cppc_cpufreq, we should check
> > cpuinfo_cur_freq but not scaling_cur_freq. So here change the
> > check sequence to make sure it works for all cpufreq drivers.
> > Besides, add rounding for pstate driver.
> >
> > Fixes: ff6dfb8e492f ("test/power: fix CPU frequency check")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Richael Zhuang <richael.zhuang@arm.com>
> Acked-by: David Hunt <david.hunt@intel.com>
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2021-07-20 15:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 8:44 [dpdk-dev] [PATCH v1 0/1] test/power: check cpuinfo cur freq before Richael Zhuang
2021-07-14 8:44 ` [dpdk-dev] [PATCH v1 1/1] test/power: check cpuinfo cur freq before scaling cur freq Richael Zhuang
2021-07-14 9:15 ` David Hunt
2021-07-14 9:23 ` Richael Zhuang
2021-07-14 10:13 ` David Hunt
2021-07-14 10:29 ` Richael Zhuang
2021-07-14 10:44 ` [dpdk-dev] [PATCH v2 0/1] test/power: fix CPU frequency check Richael Zhuang
2021-07-14 10:44 ` [dpdk-dev] [PATCH v2 1/1] " Richael Zhuang
2021-07-14 12:23 ` David Hunt
2021-07-15 1:44 ` Richael Zhuang
2021-07-20 15:20 ` David Marchand [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=CAJFAV8x6dyvRNOKQsxhJiwYE6WXH4BFpuuQFzfzqiBFFC2h04A@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=richael.zhuang@arm.com \
--cc=stable@dpdk.org \
--cc=zhiminx.huang@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).