On 16/03/2021 14:30, Jan Beulich wrote: > On 16.03.2021 04:02, Dylanger Daly wrote: >> It appears AMD Ryzen 4000 based CPUs are not supported by `xenpm`, running >> `xenpm get-cpufreq-states` returns nothing and `get-cpufreq-para` returns >> `failed to get cpufreq parameter` >> >> This was somewhat expected as Ryzen 4000 series CPUs are quite new, so as a >> workaround I tried putting `cpufreq=dom0-kernel dom0_max_vcpus=8 >> dom0_vcpus_pin` onto CMDLINE, from what I've read this should essentially >> pass control for CPU frequency scaling down to dom0's kernel (5.11.4). > Just fyi, seeing that you found a solution for your problem: I > firmly believe "cpufreq=dom0-kernel" should never have been > introduced. I'm not surprised at all if, as it looks, it stopped > working at some point.
I agree that cpufreq=dom0-kernel can't reasonably work. Lets just take it out - it doesn't serve any good tricking people into thinking it might plausibly work. ~Andrew
