On Fri, Jul 11, 2025 at 11:50:49AM +0800, Penny Zheng wrote:
> In `xenpm get-cpufreq-para `, ->freq_num and ->cpu_num checking are
> tied together via variable "has_num", while ->freq_num only has non-zero value
> when cpufreq driver in legacy P-states mode.
>
> So we drop the "has_num" condition
On 11.07.2025 05:50, Penny Zheng wrote:
> In `xenpm get-cpufreq-para `, ->freq_num and ->cpu_num checking are
> tied together via variable "has_num", while ->freq_num only has non-zero value
> when cpufreq driver in legacy P-states mode.
>
> So we drop the "has_num" condition check, and mirror the
In `xenpm get-cpufreq-para `, ->freq_num and ->cpu_num checking are
tied together via variable "has_num", while ->freq_num only has non-zero value
when cpufreq driver in legacy P-states mode.
So we drop the "has_num" condition check, and mirror the ->gov_num check for
both ->freq_num and ->cpu_num
