From: Paolo Bonzini <pbonzini@redhat.com>
To: Jim Mattson <jmattson@google.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
seanjc@google.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] KVM: x86: Do not return host topology information from KVM_GET_SUPPORTED_CPUID
Date: Thu, 26 Jan 2023 18:47:49 +0100 [thread overview]
Message-ID: <b3820c5c-370b-44f1-7dac-544e504bc61a@redhat.com> (raw)
In-Reply-To: <CALMp9eTpbwQP3QsqpOBsDb0soLpsv9FZA=ivZUmf2GJgBxhfmw@mail.gmail.com>
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
next prev parent reply other threads:[~2023-01-26 17:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 9:20 Paolo Bonzini
2023-01-24 23:16 ` Jim Mattson
2023-01-25 14:17 ` Paolo Bonzini
2023-01-25 16:47 ` Jim Mattson
2023-01-25 21:46 ` Paolo Bonzini
2023-01-25 22:09 ` Jim Mattson
2023-01-25 22:43 ` Paolo Bonzini
2023-01-26 0:58 ` Jim Mattson
2023-01-26 9:40 ` Paolo Bonzini
2023-01-26 16:06 ` Jim Mattson
2023-01-26 17:47 ` Paolo Bonzini [this message]
2023-01-26 20:45 ` Jim Mattson
2023-01-27 7:23 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b3820c5c-370b-44f1-7dac-544e504bc61a@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®