[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AMD Ryzen 4000 (Mobile) cpufreq issues
- To: Jan Beulich <jbeulich@xxxxxxxx>, Dylanger Daly <dylangerdaly@xxxxxxxxxxxxxx>
- From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
- Date: Tue, 16 Mar 2021 14:44:06 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vq1kxDCErFH3ye2opvEmexZIwiPef/LOJbwpjbGKkD4=; b=Fr/sSlQTvg3bCJ9jAlD4cR/y1OlvlmDqEzaFJoeAeRz/gYlUouU3Xc1fKFUSgKXcwNwIM4POflGXFK/c8XQBxuH4uGNYqrik/AsEGcX/qsJp6OaZvG/+QPohaus+9qsCANJuv/nKMkzkRnRU2FZLYtGoKf1jcGNhDtBdH7HBpBGekfRzjfdngEkLgdaTlEqiFa/HW5IopUo6fljGZwiPLFknK01Kw/FE/WuqYyQb8NLq8+Lbhbh59Z4xnWUCXZcLpxQDMdwpTEouALJ0737NBRe76Uqyxohpc2IoMQ+ALRf/I9qHsZ5pIL9TQy66dghntvdp7ZHYJdawaTFXU0FiMg==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=dkcjwPHUm5DSsIYvii5O9YAS7G/H7mfLtP33MNSEqwqJw/xhhq1Sj+Az4NbHl+6keEm5kxeciUPyg8MsXaA3n7EOWpEYIfTfIuvO8wDm8fNnv5MtjzokNxkkL+yuymQ3KqFAhUa3n9G6n1I1hpNm1FhhtligH59fH257/4FlGHl/6zc15t3m1GQEAK9Y98oiwDNZq5qbS34TsEvQwJ2dpVRmdAX5FPVLIf89zZivhjwd3ssQNr8WikIMTkKfP606yc8uqbpXEJzDaja4CUyjOlCim23vue5xKmSSJJpxm3Q8W5pG4ctxtJkcwVDV5W73riutAuagBkCINFbVabCyjA==
- Authentication-results: esa4.hc3370-68.iphmx.com; dkim=pass (signature verified) header.i=@citrix.onmicrosoft.com
- Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- Delivery-date: Tue, 16 Mar 2021 14:44:23 +0000
- Ironport-hdrordr: A9a23:wV8VD63j5FdizruToKyViQqjBDkkLtp033Aq2lEZdDV+dMuEm8 ey2MkKzBOcskd0ZFgMkc2NUZPwI0/02oVy5eAqXIuKeCnDlC+WIJp57Y3kqgePJwTb+vRG3a ltN4hSYeeaMXFAgcz34Ba1Hr8bqbG62ZulnOLPi0pqJDsaCJ1I1RtzCQqQDyRNNWx7LKc5D5 aV645moDetaB0sAviTO39tZYj+juyOvI76Z1o8CwQ/7g6VgXeT9KfiCBSDxH4lOQ9n8PMA8X XPkxG826Wosf2n6jK07QDuxqUTvNPgz9dZbfbgtvQo
- Ironport-sdr: VM6CGPCsYCA3ByD412LBUHkRIwcgEDGq0dW2i5G6Q5p1QE87BCv5DX6ZE3vmWC39xLL4emk/Q4 lBKT1PKibpXFPtNrKzEFmv8lHSPAIr8DDYKMJtPLjqdHua8a7LwBgLA5QMXIS2Qiyjn1DGPRmh W4duAoLFd7YlCN26kcqbiv3KXBss2cGOpKxvbwmkxSL3IyddJ9GbIVgkxMJ9PcN9vkWdzBs0/5 dHg41zI4AWRRxZD91jRe+70t5WS9zQurG9yKmjyX0mCKTnC1Usv/r5TGK71wV7+9Opm1syqR/2 R3g=
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
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
|
