mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.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,
	Alexander Graf <graf@amazon.com>
Subject: Re: [PATCH v4 0/4] KVM: x86: MSR filtering and related fixes
Date: Thu, 11 Nov 2021 15:06:13 +0100	[thread overview]
Message-ID: <15d22245-16be-9665-4d3d-91b643ff044d@redhat.com> (raw)
In-Reply-To: <20211109013047.2041518-1-seanjc@google.com>

On 11/9/21 02:30, Sean Christopherson wrote:
> Fix a nVMX MSR interception check bug, fix two intertwined nVMX bugs bugs
> related to MSR filtering (one directly, one indirectly), and additional
> cleanup on top.  The main SRCU fix from the original series was merged,
> but these got left behind (luckily, becaues the main fix was buggy).
> 
> Side topic, getting a VM to actually barf on RDMSR(SPEC_CTRL) is comically
> difficult: -spec-ctrl,-stibp,-ssbd,-ibrs-all,-ibpb,-amd-stibp,-amd-ssbd.
> QEMU and KVM really, really want to expose SPEC_CTRL to the guest :-)
> 
> v4:
>    - Rebase to 0d7d84498fb4 ("KVM: x86: SGX must obey the ... protocol")
>    - Fix inverted passthrough check for SPEC_CTRL. [Vitaly]
>    - Add patch to fix MSR bitmap enabling check in helper.
> 
> v3:
>    - Rebase to 9f6090b09d66 ("KVM: MMU: make spte .... in make_spte")
> 
> v2:
>    - https://lkml.kernel.org/r/20210318224310.3274160-1-seanjc@google.com
>    - Make the macro insanity slightly less insane. [Paolo]
> 
> v1: https://lkml.kernel.org/r/20210316184436.2544875-1-seanjc@google.com
> 
> Sean Christopherson (4):
>    KVM: nVMX: Query current VMCS when determining if MSR bitmaps are in
>      use
>    KVM: nVMX: Handle dynamic MSR intercept toggling
>    KVM: VMX: Macrofy the MSR bitmap getters and setters
>    KVM: nVMX: Clean up x2APIC MSR handling for L2
> 
>   arch/x86/kvm/vmx/nested.c | 164 +++++++++++++++-----------------------
>   arch/x86/kvm/vmx/vmx.c    |  61 ++------------
>   arch/x86/kvm/vmx/vmx.h    |  28 +++++++
>   3 files changed, 97 insertions(+), 156 deletions(-)
> 

Queued, thanks.

Paolo


      parent reply	other threads:[~2021-11-11 14:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09  1:30 Sean Christopherson
2021-11-09  1:30 ` [PATCH v4 1/4] KVM: nVMX: Query current VMCS when determining if MSR bitmaps are in use Sean Christopherson
2021-11-09  1:30 ` [PATCH v4 2/4] KVM: nVMX: Handle dynamic MSR intercept toggling Sean Christopherson
2021-11-09  1:30 ` [PATCH v4 3/4] KVM: VMX: Macrofy the MSR bitmap getters and setters Sean Christopherson
2021-11-09  1:30 ` [PATCH v4 4/4] KVM: nVMX: Clean up x2APIC MSR handling for L2 Sean Christopherson
2021-11-11 14:06 ` 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=15d22245-16be-9665-4d3d-91b643ff044d@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=graf@amazon.com \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seanjc@google.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 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®