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, rkrcmar@kernel.org
Subject: [GIT PULL] KVM fixes for Linux 5.16-rc6
Date: Sun, 19 Dec 2021 20:16:08 +0100	[thread overview]
Message-ID: <20211219191608.265537-1-pbonzini@redhat.com> (raw)

Linus,

The following changes since commit 10e7a099bfd860a2b77ea8aaac661f52c16dd865:

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

are available in the Git repository at:

  git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus

for you to fetch changes up to 18c841e1f4112d3fb742aca3429e84117fcb1e1c:

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

----------------------------------------------------------------
Two small fixes, one of which was being worked around in selftests.

----------------------------------------------------------------
Sean Christopherson (1):
      KVM: x86: Retry page fault if MMU reload is pending and root has no sp

Vitaly Kuznetsov (2):
      KVM: x86: Drop guest CPUID check for host initiated writes to MSR_IA32_PERF_CAPABILITIES
      KVM: selftests: vmx_pmu_msrs_test: Drop tests mangling guest visible CPUIDs

 arch/x86/kvm/mmu/mmu.c                                 | 16 +++++++++++++++-
 arch/x86/kvm/x86.c                                     |  2 +-
 tools/testing/selftests/kvm/x86_64/vmx_pmu_msrs_test.c | 17 -----------------
 3 files changed, 16 insertions(+), 19 deletions(-)

             reply	other threads:[~2021-12-19 19:16 UTC|newest]

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