mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: [GIT PULL] KVM fixes for Linux 5.16-rc7 (and likely final)
Date: Tue, 21 Dec 2021 13:32:01 -0500	[thread overview]
Message-ID: <20211221183201.307603-1-pbonzini@redhat.com> (raw)

Linus,

The following changes since commit 18c841e1f4112d3fb742aca3429e84117fcb1e1c:

  KVM: x86: Retry page fault if MMU reload is pending and root has no sp (2021-12-19 19:38:58 +0100)

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 fdba608f15e2427419997b0898750a49a735afcb:

  KVM: VMX: Wake vCPU when delivering posted IRQ even if vCPU == this vCPU (2021-12-21 12:39:03 -0500)

----------------------------------------------------------------
* Fix for compilation of selftests on non-x86 architectures
* Fix for kvm_run->if_flag on SEV-ES
* Fix for page table use-after-free if yielding during exit_mm()
* Improve behavior when userspace starts a nested guest with invalid state
* Fix missed wakeup with assigned devices but no VT-d posted interrupts
* Do not tell userspace to save/restore an unsupported PMU MSR

----------------------------------------------------------------

So, 5.16 really was a huge bug shakedown for KVM.  Apart from the locking
changes in -rc4, almost everything that went in after -rc2 was Cc'ed
stable, including this pull request (which I guess is not a bad thing
for rc7).

You can't quite see it, but things do seem to have calmed down; these
patches as well as those in rc6 had actually been submitted a week or
so ago; one was a relatively old 5.17 change that turned out to fix a
bug.  Since I'm taking some time off until right before the merge
window, I don't expect any more changes in 5.16.  Thanks for putting up
with this weird KVM release cycle.

Paolo

Andrew Jones (1):
      selftests: KVM: Fix non-x86 compiling

Marc Orr (1):
      KVM: x86: Always set kvm_run->if_flag

Sean Christopherson (6):
      KVM: x86/mmu: Don't advance iterator after restart due to yielding
      KVM: VMX: Always clear vmx->fail on emulation_required
      KVM: nVMX: Synthesize TRIPLE_FAULT for L2 if emulation is required
      KVM: VMX: Fix stale docs for kvm-intel.emulate_invalid_guest_state
      KVM: selftests: Add test to verify TRIPLE_FAULT on invalid L2 guest state
      KVM: VMX: Wake vCPU when delivering posted IRQ even if vCPU == this vCPU

Wei Wang (1):
      KVM: x86: remove PMU FIXED_CTR3 from msrs_to_save_all

 Documentation/admin-guide/kernel-parameters.txt    |   8 +-
 arch/x86/include/asm/kvm-x86-ops.h                 |   1 +
 arch/x86/include/asm/kvm_host.h                    |   1 +
 arch/x86/kvm/mmu/tdp_iter.c                        |   6 ++
 arch/x86/kvm/mmu/tdp_iter.h                        |   6 ++
 arch/x86/kvm/mmu/tdp_mmu.c                         |  29 +++---
 arch/x86/kvm/svm/svm.c                             |  21 +++--
 arch/x86/kvm/vmx/vmx.c                             |  45 ++++++---
 arch/x86/kvm/x86.c                                 |  11 +--
 tools/testing/selftests/kvm/.gitignore             |   1 +
 tools/testing/selftests/kvm/Makefile               |   1 +
 tools/testing/selftests/kvm/include/kvm_util.h     |  10 +-
 tools/testing/selftests/kvm/lib/kvm_util.c         |   5 +
 .../kvm/x86_64/vmx_invalid_nested_guest_state.c    | 105 +++++++++++++++++++++
 14 files changed, 195 insertions(+), 55 deletions(-)
 create mode 100644 tools/testing/selftests/kvm/x86_64/vmx_invalid_nested_guest_state.c


             reply	other threads:[~2021-12-21 18:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21 18:32 Paolo Bonzini [this message]
2021-12-21 20:36 ` 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=20211221183201.307603-1-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®