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-rc5
Date: Fri, 10 Dec 2021 09:50:44 -0500	[thread overview]
Message-ID: <20211210145044.28699-1-pbonzini@redhat.com> (raw)

Linus,

The following changes since commit 0fcfb00b28c0b7884635dacf38e46d60bf3d4eb1:

  Linux 5.16-rc4 (2021-12-05 14:08:22 -0800)

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 10e7a099bfd860a2b77ea8aaac661f52c16dd865:

  selftests: KVM: Add test to verify KVM doesn't explode on "bad" I/O (2021-12-10 09:38:02 -0500)

----------------------------------------------------------------
More x86 fixes:
* Logic bugs in CR0 writes and Hyper-V hypercalls
* Don't use Enlightened MSR Bitmap for L3
* Remove user-triggerable WARN

Plus a few selftest fixes and a regression test for the
user-triggerable WARN.

----------------------------------------------------------------
So I am not sure if this counts as "the kvm side calming down"; but the
larger scale bugfixes are all in-tree now, and what I've got here looks
(at least on the arch/ side) like a fairly normal pull request for
middle RCs.

Thanks,

Paolo

Lai Jiangshan (1):
      KVM: X86: Raise #GP when clearing CR0_PG in 64 bit mode

Maciej S. Szmigiero (1):
      KVM: x86: selftests: svm_int_ctl_test: fix intercept calculation

Paolo Bonzini (1):
      selftests: KVM: avoid failures due to reserved HyperTransport region

Sean Christopherson (3):
      KVM: x86: Ignore sparse banks size for an "all CPUs", non-sparse IPI req
      KVM: x86: Don't WARN if userspace mucks with RCX during string I/O exit
      selftests: KVM: Add test to verify KVM doesn't explode on "bad" I/O

Vitaly Kuznetsov (2):
      KVM: nVMX: Don't use Enlightened MSR Bitmap for L3
      KVM: x86: Wait for IPIs to be delivered when handling Hyper-V TLB flush hypercall

 arch/x86/include/asm/kvm_host.h                    |   2 +-
 arch/x86/kvm/hyperv.c                              |   7 +-
 arch/x86/kvm/vmx/vmx.c                             |  22 ++--
 arch/x86/kvm/x86.c                                 |  12 ++-
 tools/testing/selftests/kvm/.gitignore             |   1 +
 tools/testing/selftests/kvm/Makefile               |   1 +
 tools/testing/selftests/kvm/include/kvm_util.h     |   9 ++
 tools/testing/selftests/kvm/lib/kvm_util.c         |   2 +-
 tools/testing/selftests/kvm/lib/x86_64/processor.c |  68 ++++++++++++
 .../selftests/kvm/x86_64/svm_int_ctl_test.c        |   2 +-
 .../selftests/kvm/x86_64/userspace_io_test.c       | 114 +++++++++++++++++++++
 11 files changed, 223 insertions(+), 17 deletions(-)
 create mode 100644 tools/testing/selftests/kvm/x86_64/userspace_io_test.c


             reply	other threads:[~2021-12-10 14:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 14:50 Paolo Bonzini [this message]
2021-12-10 22:46 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2021-12-10 14:50 Paolo Bonzini

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=20211210145044.28699-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®