From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Aaron Lewis <aaronlewis@google.com>,
kvm@vger.kernel.org, jmattson@google.com
Subject: Re: [RFC PATCH] KVM: x86: Protect the unused bits in MSR exiting flags
Date: Tue, 19 Jul 2022 18:55:01 +0000 [thread overview]
Message-ID: <Ytb+BZReuuD+2rpd@google.com> (raw)
In-Reply-To: <8da08a8a-e639-301d-ca98-d85b74c1ad20@redhat.com>
On Tue, Jul 19, 2022, Paolo Bonzini wrote:
> On 7/14/22 18:13, Aaron Lewis wrote:
> > ---
> >
> > Posting as an RFC to get feedback whether it's too late to protect the
> > unused flag bits. My hope is this feature is still new enough, and not
> > widely used enough, and this change is reasonable enough to be able to be
> > corrected. These bits should have been protected from the start, but
> > unfortunately they were not.
> >
> > Another option would be to correct this by adding a quirk, but fixing
> > it that has its down sides. It complicates the code more than it
> > would otherwise be, and complicates the usage for anyone using any new
> > features introduce in the future because they would also have to enable
> > a quirk. For long term simplicity my hope is to be able to just patch
> > the original change.
>
> Yes, let's do it this way.
Heh, which way is "this way"?
(a) Fix KVM_CAP_X86_USER_SPACE_MSR and cross our fingers
(b) Add a quirk
(c) ???
next prev parent reply other threads:[~2022-07-19 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 16:13 [RFC PATCH] KVM: x86: Protect the unused bits in MSR exiting flags Aaron Lewis
2022-07-14 21:56 ` Sean Christopherson
2022-07-19 18:04 ` Paolo Bonzini
2022-07-19 18:55 ` Sean Christopherson [this message]
2022-07-19 19:47 ` Aaron Lewis
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=Ytb+BZReuuD+2rpd@google.com \
--to=seanjc@google.com \
--cc=aaronlewis@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.