From: Liang Ma <liangma@liangbit.com>
To: Richael Zhuang <richael.zhuang@arm.com>
Cc: dev@dpdk.org, alan.carew@intel.com, stable@dpdk.org,
David Hunt <david.hunt@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v3 3/3] test/power: add delay before checking cpuinfo cur freq
Date: Wed, 7 Apr 2021 11:14:38 +0100 [thread overview]
Message-ID: <YG2GDuV9B71bcGpA@C02F33EJML85> (raw)
In-Reply-To: <20210407074636.26891-4-richael.zhuang@arm.com>
On Wed, Apr 07, 2021 at 03:46:36PM +0800, Richael Zhuang wrote:
> Sleep for 1s before checking the newly updated value from
> "/sys/devices/system/cpu/cpu%u/cpufreq/cpuinfo_cur_freq", because
> for some systems it may not be effective immediately.
>
> Fixes: ed7c51a6a680 ("app/test: vm power management")
> Cc: alan.carew@intel.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Richael Zhuang <richael.zhuang@arm.com>
> ---
> app/test/test_power_cpufreq.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/app/test/test_power_cpufreq.c b/app/test/test_power_cpufreq.c
> index cda74bd8a..7a93bc90a 100644
> --- a/app/test/test_power_cpufreq.c
> +++ b/app/test/test_power_cpufreq.c
> @@ -47,6 +47,9 @@ static uint32_t freqs[TEST_POWER_FREQS_NUM_MAX];
> static int
> check_cur_freq(unsigned lcore_id, uint32_t idx)
> {
> + /* wait for the value to be updated */
> + sleep(1);
Hi Richael,
1 second looks way too much for CPU frequency swap.
The unit should be ms in the worst case regardless the vendor, IMO.
Regards
Liang
> +
> #define TEST_POWER_CONVERT_TO_DECIMAL 10
> FILE *f;
> char fullpath[PATH_MAX];
> --
> 2.20.1
>
next prev parent reply other threads:[~2021-04-07 10:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 3:04 [dpdk-stable] [PATCH v1 2/2] test/power: fix a bug in cpufreq autotest Richael Zhuang
2021-04-06 3:41 ` Richael Zhuang
2021-04-07 2:39 ` [dpdk-stable] [PATCH v2 " Richael Zhuang
[not found] ` <20210407074636.26891-1-richael.zhuang@arm.com>
2021-04-07 7:46 ` [dpdk-stable] [PATCH v3 1/3] test/power: round cpuinfo cur freq value " Richael Zhuang
[not found] ` <20210415053923.3447-1-richael.zhuang@arm.com>
2021-04-15 5:39 ` [dpdk-stable] [PATCH v4 1/2] " Richael Zhuang
2021-04-15 5:39 ` [dpdk-stable] [PATCH v4 2/2] test/power: add delay before checking cpuinfo cur freq Richael Zhuang
[not found] ` <20210415055930.3899-1-richael.zhuang@arm.com>
2021-04-15 5:59 ` [dpdk-stable] [PATCH v5 1/2] " Richael Zhuang
2021-04-20 12:38 ` David Hunt
2021-04-20 13:15 ` David Hunt
2021-04-21 2:41 ` Richael Zhuang
2021-04-15 5:59 ` [dpdk-stable] [PATCH v5 2/2] test/power: round cpuinfo cur freq value in cpufreq autotest Richael Zhuang
2021-04-20 14:01 ` David Hunt
2021-04-07 7:46 ` [dpdk-stable] [PATCH v3 2/3] test/power: fix a bug " Richael Zhuang
2021-04-07 9:58 ` [dpdk-stable] [dpdk-dev] " Burakov, Anatoly
2021-04-08 2:10 ` Richael Zhuang
2021-04-08 14:55 ` Burakov, Anatoly
2021-04-14 8:29 ` Richael Zhuang
2021-04-07 7:46 ` [dpdk-stable] [PATCH v3 3/3] test/power: add delay before checking cpuinfo cur freq Richael Zhuang
2021-04-07 10:14 ` Liang Ma [this message]
2021-04-08 5:10 ` [dpdk-stable] [dpdk-dev] " Richael Zhuang
2021-04-08 5:16 ` Richael Zhuang
2021-04-08 7:54 ` Liang Ma
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=YG2GDuV9B71bcGpA@C02F33EJML85 \
--to=liangma@liangbit.com \
--cc=alan.carew@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=richael.zhuang@arm.com \
--cc=stable@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).