From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] KVM: VMX: CR0/CR4 guest/host masks cleanup
Date: Fri, 3 Jul 2020 18:16:39 +0200 [thread overview]
Message-ID: <3ad927c2-d02e-3739-f37a-2fd75a3ebb97@redhat.com> (raw)
In-Reply-To: <20200703040422.31536-1-sean.j.christopherson@intel.com>
On 03/07/20 06:04, Sean Christopherson wrote:
> Fix a bug where CR4.TSD isn't correctly marked as being possibly owned by
> the guest in the common x86 macro, then clean up the mess that made the
> bug possible by throwing away VMX's mix of duplicate code and open coded
> tweaks. The lack of a define for the guest-owned CR0 bit has bugged me
> for a long time, but adding another define always seemed ridiculous.
>
> Sean Christopherson (2):
> KVM: x86: Mark CR4.TSD as being possibly owned by the guest
> KVM: VMX: Use KVM_POSSIBLE_CR*_GUEST_BITS to initialize guest/host
> masks
>
> arch/x86/kvm/kvm_cache_regs.h | 2 +-
> arch/x86/kvm/vmx/nested.c | 4 ++--
> arch/x86/kvm/vmx/vmx.c | 13 +++++--------
> 3 files changed, 8 insertions(+), 11 deletions(-)
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2020-07-03 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 4:04 [PATCH 0/2] KVM: VMX: CR0/CR4 guest/host masks cleanup Sean Christopherson
2020-07-03 4:04 ` [PATCH 1/2] KVM: x86: Mark CR4.TSD as being possibly owned by the guest Sean Christopherson
2020-07-03 4:04 ` [PATCH 2/2] KVM: VMX: Use KVM_POSSIBLE_CR*_GUEST_BITS to initialize guest/host masks Sean Christopherson
2020-07-03 16:16 ` Paolo Bonzini [this message]
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=3ad927c2-d02e-3739-f37a-2fd75a3ebb97@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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.