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 changes for Linux 5.7-rc6
Date: Sat, 16 May 2020 08:24:13 -0400	[thread overview]
Message-ID: <20200516122413.693424-1-pbonzini@redhat.com> (raw)

Linus,

The following changes since commit 2673cb6849722a4ffd74c27a9200a9ec43f64be3:

  Merge tag 'kvm-s390-master-5.7-3' of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux into HEAD (2020-05-06 08:09:17 -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 c4e0e4ab4cf3ec2b3f0b628ead108d677644ebd9:

  KVM: x86: Fix off-by-one error in kvm_vcpu_ioctl_x86_setup_mce (2020-05-15 13:48:56 -0400)

----------------------------------------------------------------
A new testcase for guest debugging (gdbstub) that exposed a bunch of
bugs, mostly for AMD processors.  And a few other x86 fixes.

----------------------------------------------------------------
Babu Moger (1):
      KVM: x86: Fix pkru save/restore when guest CR4.PKE=0, move it to x86.c

Jim Mattson (1):
      KVM: x86: Fix off-by-one error in kvm_vcpu_ioctl_x86_setup_mce

Paolo Bonzini (6):
      KVM: x86: fix DR6 delivery for various cases of #DB injection
      KVM: nSVM: trap #DB and #BP to userspace if guest debugging is on
      KVM: SVM: keep DR6 synchronized with vcpu->arch.dr6
      KVM: x86, SVM: isolate vcpu->arch.dr6 from vmcb->save.dr6
      KVM: VMX: pass correct DR6 for GD userspace exit
      Merge branch 'kvm-amd-fixes' into HEAD

Peter Xu (4):
      KVM: X86: Declare KVM_CAP_SET_GUEST_DEBUG properly
      KVM: X86: Set RTM for DB_VECTOR too for KVM_EXIT_DEBUG
      KVM: X86: Fix single-step with KVM_SET_GUEST_DEBUG
      KVM: selftests: Add KVM_SET_GUEST_DEBUG test

Suravee Suthikulpanit (2):
      KVM: Introduce kvm_make_all_cpus_request_except()
      KVM: SVM: Disable AVIC before setting V_IRQ

 arch/x86/include/asm/kvm_host.h                 |   4 +-
 arch/x86/kvm/hyperv.c                           |   2 +-
 arch/x86/kvm/svm/nested.c                       |  39 ++++-
 arch/x86/kvm/svm/svm.c                          |  36 +++--
 arch/x86/kvm/vmx/vmx.c                          |  41 +----
 arch/x86/kvm/x86.c                              |  60 ++++---
 include/linux/kvm_host.h                        |   3 +
 tools/testing/selftests/kvm/Makefile            |   1 +
 tools/testing/selftests/kvm/include/kvm_util.h  |   2 +
 tools/testing/selftests/kvm/lib/kvm_util.c      |   9 ++
 tools/testing/selftests/kvm/x86_64/debug_regs.c | 202 ++++++++++++++++++++++++
 virt/kvm/kvm_main.c                             |  14 +-
 12 files changed, 325 insertions(+), 88 deletions(-)
 create mode 100644 tools/testing/selftests/kvm/x86_64/debug_regs.c


             reply	other threads:[~2020-05-16 12:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16 12:24 Paolo Bonzini [this message]
2020-05-17  4:45 ` 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=20200516122413.693424-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®