[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b3820c5c-370b-44f1-7dac-544e504bc61a@redhat.com>
Date: Thu, 26 Jan 2023 18:47:49 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Jim Mattson <jmattson@...gle.com>
Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
seanjc@...gle.com, stable@...r.kernel.org
Subject: Re: [PATCH v2] KVM: x86: Do not return host topology information from
KVM_GET_SUPPORTED_CPUID
On 1/26/23 17:06, Jim Mattson wrote:
>>> Sadly, there isn't a single kernel involved. People running our VMM on
>>> their desktops are going to be impacted as soon as this patch hits
>>> that distro. (I don't know if I can say which distro that is.) So, now
>>> we have to get the VMM folks to urgently accommodate this change and
>>> get a new distribution out.
>>
>> Ok, this is what is needed to make a more informed choice. To be clear,
>> this is _still_ not public (for example it's not ChromeOS), so there is
>> at least some control on what version of the VMM they use? Would it
>> make sense to buy you a few months by deferring this patch to Linux 6.3-6.5?
>
> Mainline isn't a problem. I'm more worried about 5.19 LTS.
5.19 is not LTS, is it? This patch is only in 6.1.7 and 6.1.8 as far as
stable kernels is concerned, should I ask Greg to revert it there?
Paolo
Powered by blists - more mailing lists