kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org
Subject: Re: [GIT PULL] KVM updates for Linux 5.13-rc2
Date: Mon, 10 May 2021 19:09:44 +0000	[thread overview]
Message-ID: <YJmE+NpAt4GTw/ZK@google.com> (raw)
In-Reply-To: <20210510181441.351452-1-pbonzini@redhat.com>

On Mon, May 10, 2021, Paolo Bonzini wrote:
> Linus,
> 
> The following changes since commit 9ccce092fc64d19504fa54de4fd659e279cc92e7:
> 
>   Merge tag 'for-linus-5.13-ofs-1' of git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux (2021-05-02 14:13:46 -0700)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
> 
> for you to fetch changes up to ce7ea0cfdc2e9ff31d12da31c3226deddb9644f5:
> 
>   KVM: SVM: Move GHCB unmapping to fix RCU warning (2021-05-07 06:06:23 -0400)
> 
> Thomas Gleixner and Michael Ellerman had some KVM changes in their
> late merge window pull requests, but there are no conflicts.
> 
> ----------------------------------------------------------------
> Sean Christopherson (17):
>       KVM: VMX: Do not advertise RDPID if ENABLE_RDTSCP control is unsupported
>       KVM: x86: Emulate RDPID only if RDTSCP is supported
>       KVM: SVM: Inject #UD on RDTSCP when it should be disabled in the guest
>       KVM: x86: Move RDPID emulation intercept to its own enum
>       KVM: VMX: Disable preemption when probing user return MSRs
>       KVM: SVM: Probe and load MSR_TSC_AUX regardless of RDTSCP support in host
>       KVM: x86: Add support for RDPID without RDTSCP
>       KVM: VMX: Configure list of user return MSRs at module init

I'm guessing I'm too late as usual and the hashes are set in stone, but just in
case I'm not...

This patch (commit b6194b94a2ca, "KVM: VMX: Configure...) has a bug that Maxim
found during code review.  The bug is eliminated by the very next patch (commit
e7f5ab87841c), but it will break bisection if bisection involves running a KVM
guest.  At a glance, even syzkaller will be affected :-(

>       KVM: VMX: Use flag to indicate "active" uret MSRs instead of sorting list
>       KVM: VMX: Use common x86's uret MSR list as the one true list
>       KVM: VMX: Disable loading of TSX_CTRL MSR the more conventional way
>       KVM: x86: Export the number of uret MSRs to vendor modules
>       KVM: x86: Move uret MSR slot management to common x86
>       KVM: x86: Tie Intel and AMD behavior for MSR_TSC_AUX to guest CPU model
>       KVM: x86: Hide RDTSCP and RDPID if MSR_TSC_AUX probing failed
>       KVM: x86: Prevent KVM SVM from loading on kernels with 5-level paging
>       KVM: SVM: Invert user pointer casting in SEV {en,de}crypt helpers

  reply	other threads:[~2021-05-10 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 18:14 [GIT PULL] KVM updates for Linux 5.13-rc2 Paolo Bonzini
2021-05-10 19:09 ` Sean Christopherson [this message]
2021-05-10 20:12 ` pr-tracker-bot

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=YJmE+NpAt4GTw/ZK@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).