All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, rkrcmar@redhat.com, kvm@vger.kernel.org
Subject: [GIT PULL] Final batch of KVM changes for Linux 5.3.
Date: Sat, 14 Sep 2019 22:31:41 +0200	[thread overview]
Message-ID: <1568493101-32728-1-git-send-email-pbonzini@redhat.com> (raw)

Linus,

The following changes since commit a7f89616b7376495424f682b6086e0c391a89a1d:

  Merge branch 'for-5.3-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup (2019-09-13 09:52:01 +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 a9c20bb0206ae9384bd470a6832dd8913730add9:

  Merge tag 'kvm-s390-master-5.3-1' of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux into kvm-master (2019-09-14 09:25:30 +0200)

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

The main change here is a revert of reverts.  We recently simplified some
code that was thought unnecessary; however, since then KVM has grown quite
a few cond_resched()s and for that reason the simplified code is prone to
livelocks---one CPUs tries to empty a list of guest page tables while the
others keep adding to them.  This adds back the generation-based zapping of
guest page tables, which was not unnecessary after all.

On top of this, there is a fix for a kernel memory leak and a couple of
s390 fixlets as well.

----------------------------------------------------------------
Fuqian Huang (1):
      KVM: x86: work around leak of uninitialized stack contents

Igor Mammedov (1):
      KVM: s390: kvm_s390_vm_start_migration: check dirty_bitmap before using it as target for memset()

Paolo Bonzini (2):
      KVM: nVMX: handle page fault in vmread
      Merge tag 'kvm-s390-master-5.3-1' of git://git.kernel.org/.../kvms390/linux into kvm-master

Sean Christopherson (1):
      KVM: x86/mmu: Reintroduce fast invalidate/zap for flushing memslot

Thomas Huth (1):
      KVM: s390: Do not leak kernel stack data in the KVM_S390_INTERRUPT ioctl

 arch/s390/kvm/interrupt.c       |  10 ++++
 arch/s390/kvm/kvm-s390.c        |   4 +-
 arch/x86/include/asm/kvm_host.h |   2 +
 arch/x86/kvm/mmu.c              | 101 +++++++++++++++++++++++++++++++++++++++-
 arch/x86/kvm/vmx/nested.c       |   4 +-
 arch/x86/kvm/x86.c              |   7 +++
 6 files changed, 124 insertions(+), 4 deletions(-)

             reply	other threads:[~2019-09-14 20:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-14 20:31 Paolo Bonzini [this message]
2019-09-14 23:25 ` [GIT PULL] Final batch of KVM changes for Linux 5.3 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=1568493101-32728-1-git-send-email-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkrcmar@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.