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.ca...@intel.com
> Cc: sta...@dpdk.org
>
> Signed-off-by: Richael Zhuang <richael.zhu...@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
>