For some platforms the newly-set frequency may not be effective
immediately. If we didn't get the right value from cpuinfo_cur_freq
immediately, add 10ms delay each time before rechecking until
timeout.
>From our test, for some arm platforms, it requires up to 700ms when
going from a minimum to a
On 15/4/2021 6:59 AM, Richael Zhuang wrote:
For some platforms the newly-set frequency may not be effective
immediately. If we didn't get the right value from cpuinfo_cur_freq
immediately, add 10ms delay each time before rechecking until
timeout.
From our test, for some arm platforms, it requ
On 20/4/2021 1:38 PM, David Hunt wrote:
On 15/4/2021 6:59 AM, Richael Zhuang wrote:
For some platforms the newly-set frequency may not be effective
immediately. If we didn't get the right value from cpuinfo_cur_freq
immediately, add 10ms delay each time before rechecking until
timeout.
From
> -Original Message-
> From: David Hunt
> Sent: Tuesday, April 20, 2021 8:39 PM
> To: Richael Zhuang ; dev@dpdk.org
> Cc: nd ; alan.ca...@intel.com; sta...@dpdk.org; Pablo de
> Lara
> Subject: Re: [PATCH v5 1/2] test/power: add delay before checking cpuinfo
> cur freq
>
>
> On 15/4/202
4 matches
Mail list logo
