> -Original Message-
> From: David Hunt
> Sent: Wednesday, July 14, 2021 6:14 PM
> To: Richael Zhuang ; dev@dpdk.org
> Cc: zhiminx.hu...@intel.com; sta...@dpdk.org; nd
> Subject: Re: [PATCH v1 1/1] test/power: check cpuinfo cur freq before scaling
> cur freq
>
>
> On 14/7/2021 10:23 A
On 14/7/2021 10:23 AM, Richael Zhuang wrote:
-Original Message-
From: David Hunt
Sent: Wednesday, July 14, 2021 5:15 PM
To: Richael Zhuang ; dev@dpdk.org
Cc: zhiminx.hu...@intel.com; sta...@dpdk.org
Subject: Re: [PATCH v1 1/1] test/power: check cpuinfo cur freq before scaling
cur fre
> -Original Message-
> From: David Hunt
> Sent: Wednesday, July 14, 2021 5:15 PM
> To: Richael Zhuang ; dev@dpdk.org
> Cc: zhiminx.hu...@intel.com; sta...@dpdk.org
> Subject: Re: [PATCH v1 1/1] test/power: check cpuinfo cur freq before scaling
> cur freq
>
>
> On 14/7/2021 9:44 AM, Ric
On 14/7/2021 9: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
c
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. So here checking cpuinfo_cur_fr
5 matches
Mail list logo