linux-kernel.vger.kernel.org archive mirror
 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.14-rc5
Date: Thu,  5 Aug 2021 03:39:58 -0400	[thread overview]
Message-ID: <20210805073958.2684067-1-pbonzini@redhat.com> (raw)

Linus,

The following changes since commit 8750f9bbda115f3f79bfe43be85551ee5e12b6ff:

  KVM: add missing compat KVM_CLEAR_DIRTY_LOG (2021-07-27 16:59:01 -0400)

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

  KVM: x86/mmu: Fix per-cpu counter corruption on 32-bit builds (2021-08-05 03:33:56 -0400)

----------------------------------------------------------------
Mostly bugfixes; plus, support for XMM arguments to Hyper-V hypercalls
now obeys KVM_CAP_HYPERV_ENFORCE_CPUID.  Both the XMM arguments feature
and KVM_CAP_HYPERV_ENFORCE_CPUID are new in 5.14, and each did not know
of the other.

----------------------------------------------------------------
Maxim Levitsky (1):
      KVM: selftests: fix hyperv_clock test

Mingwei Zhang (1):
      KVM: SVM: improve the code readability for ASID management

Paolo Bonzini (2):
      KVM: x86: accept userspace interrupt only if no event is injected
      KVM: Do not leak memory for duplicate debugfs directories

Sean Christopherson (2):
      KVM: SVM: Fix off-by-one indexing when nullifying last used SEV VMCB
      KVM: x86/mmu: Fix per-cpu counter corruption on 32-bit builds

Vitaly Kuznetsov (4):
      KVM: x86: hyper-v: Check access to hypercall before reading XMM registers
      KVM: x86: Introduce trace_kvm_hv_hypercall_done()
      KVM: x86: hyper-v: Check if guest is allowed to use XMM registers for hypercall input
      KVM: selftests: Test access to XMM fast hypercalls

 arch/x86/kvm/hyperv.c                              | 18 +++++++--
 arch/x86/kvm/mmu/mmu.c                             |  2 +-
 arch/x86/kvm/svm/sev.c                             | 45 ++++++++++++----------
 arch/x86/kvm/trace.h                               | 15 ++++++++
 arch/x86/kvm/x86.c                                 | 13 ++++++-
 .../testing/selftests/kvm/include/x86_64/hyperv.h  |  5 ++-
 tools/testing/selftests/kvm/x86_64/hyperv_clock.c  |  2 +-
 .../testing/selftests/kvm/x86_64/hyperv_features.c | 41 ++++++++++++++++++--
 virt/kvm/kvm_main.c                                | 18 ++++++++-
 9 files changed, 125 insertions(+), 34 deletions(-)


             reply	other threads:[~2021-08-05  7:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05  7:39 Paolo Bonzini [this message]
2021-08-05 19:26 ` [GIT PULL] KVM fixes for Linux 5.14-rc5 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=20210805073958.2684067-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;
as well as URLs for NNTP newsgroup(s).