From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
oliver.upton@linux.dev
Subject: Re: [PATCH] Revert "KVM: nVMX: Do not expose MPX VMX controls when guest MPX disabled"
Date: Fri, 22 Jul 2022 17:23:49 +0000 [thread overview]
Message-ID: <YtrdJWmk/2RkcQi7@google.com> (raw)
In-Reply-To: <0f8dde12-576b-1579-38c9-496306aeeb81@redhat.com>
On Fri, Jul 22, 2022, Paolo Bonzini wrote:
> On 7/22/22 17:27, Sean Christopherson wrote:
> > > So revert it, at the potential cost
> > > of breaking L1s with a 6 year old kernel.
> > I would further qualify this with "breaking L1s with an_unpatched_ 6 year old
> > kernel". That fix was tagged for stable and made it way to at least the 4.9 and
> > 4.4 LTS releases.
> >
>
> Well, there _are_ people that use very old kernels and keep them up-to-date
> with fixes for only critical CVEs (for example by, ehm, paying my employer
> to do so).
Heh, I'm sure that's a winning strategy.
> But still it's way way unlikely for them to be used as L1 in a nested setup,
> whether on their own hardware or in the cloud.
>
> I pushed everything to kvm/queue, but depending on what you post it may be
> deferred to 5.21.
Can you drop the PERF_GLOBAL_CTRL revert? I figured out how to achieve what you
intended, but in a more robust (and IMO more logical) manner.
If you don't drop it before I concoct the series, I'll just include a throwaway
patch to revert it.
next prev parent reply other threads:[~2022-07-22 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 10:43 Paolo Bonzini
2022-07-22 15:27 ` Sean Christopherson
2022-07-22 17:18 ` Paolo Bonzini
2022-07-22 17:23 ` Sean Christopherson [this message]
2022-07-22 17:34 ` Paolo Bonzini
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=YtrdJWmk/2RkcQi7@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
/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®