From: Richael Zhuang <richael.zhuang@arm.com>
To: ruifeng.wang@arm.com
Cc: alan.carew@intel.com, stable@dpdk.org
Subject: [dpdk-stable] [PATCH v3 3/3] test/power: sleep 1s before check cpuinfo_cur_freq
Date: Wed, 7 Apr 2021 14:41:11 +0800 [thread overview]
Message-ID: <20210407064111.51832-4-richael.zhuang@arm.com> (raw)
In-Reply-To: <20210407064111.51832-1-richael.zhuang@arm.com>
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);
+
#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 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210407064111.51832-1-richael.zhuang@arm.com>
2021-04-07 6:41 ` [dpdk-stable] [PATCH v3 1/3] test/power: round cpuinfo_cur_freq value in cpufreq autotest Richael Zhuang
2021-04-07 6:41 ` [dpdk-stable] [PATCH v3 2/3] test/power: fix a bug " Richael Zhuang
2021-04-07 6:41 ` Richael Zhuang [this message]
[not found] <20210407063822.35858-1-richael.zhuang@arm.com>
2021-04-07 6:38 ` [dpdk-stable] [PATCH v3 3/3] test/power: sleep 1s before check cpuinfo_cur_freq 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=20210407064111.51832-4-richael.zhuang@arm.com \
--to=richael.zhuang@arm.com \
--cc=alan.carew@intel.com \
--cc=ruifeng.wang@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).