public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: [GIT PULL] KVM leftovers for 4.8-rc1
Date: Mon, 25 Jul 2016 18:03:16 +0200	[thread overview]
Message-ID: <20160725160316.GA30454@potion> (raw)

Linus,

this pull request is a combination of two pull requests for 4.7-rc8 that
were not merged due to looking hairy.  I have changed the tag message to
focus on circumstances of contained reverts as they were likely the
reason behind rejection.

First batch of 4.8-rc1 patches from kvm/next is coming later this week.

The following changes since commit a99cde438de0c4c0cecc1d1af1a55a75b10bfdef:

  Linux 4.7-rc6 (2016-07-03 23:01:00 -0700)

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 4c47eb1c18c38b755eb4894a6ca38f834de3ec23:

  arm64: KVM: VHE: Context switch MDSCR_EL1 (2016-07-23 18:07:12 +0200)

----------------------------------------------------------------
This merge introduces three patches that are later reverted,

 - Switching of MSR_TSC_AUX in SVM was thought to cause a host
   misbehavior, but it was later cleared of those doubts and the patch
   moved code to a hot path, so we reverted it.  That patch also needed
   a fix for 32 bit builds and both were reverted in one go.

 - Al Viro noticed that a fix for a leak in an error path was not valid
   with the given API and provided a better fix, so the original patch
   was reverted.

Then there are two VMX fixes that move code around because VMCS was not
accessed between vcpu_load() and vcpu_put(), a simple ARM VHE fix, and
two one-liners for PML and MTRR.

----------------------------------------------------------------
Al Viro (1):
      KVM: don't use anon_inode_getfd() before possible failures

Alexis Dambricourt (1):
      KVM: MTRR: fix kvm_mtrr_check_gfn_range_consistency page fault

Cao, Lei (1):
      KVM: VMX: handle PML full VMEXIT that occurs during event delivery

Jim Mattson (1):
      KVM: nVMX: Fix memory corruption when using VMCS shadowing

Liu Shuo (1):
      KVM: release anon file in failure path of vm creation

Marc Zyngier (1):
      arm64: KVM: VHE: Context switch MDSCR_EL1

Paolo Bonzini (3):
      KVM: SVM: fix trashing of MSR_TSC_AUX
      Revert "KVM: release anon file in failure path of vm creation"
      KVM: SVM: do not set MSR_TSC_AUX on 32-bit builds

Peter Feiner (1):
      kvm: vmx: ensure VMCS is current while enabling PML

Radim Krčmář (1):
      Revert "KVM: SVM: fix trashing of MSR_TSC_AUX"

 arch/arm64/kvm/hyp/sysreg-sr.c |  8 ++---
 arch/x86/kvm/mtrr.c            |  1 +
 arch/x86/kvm/vmx.c             | 76 +++++++++++++++++++++++-------------------
 virt/kvm/kvm_main.c            | 15 +++++++--
 4 files changed, 60 insertions(+), 40 deletions(-)

                 reply	other threads:[~2016-07-25 16:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160725160316.GA30454@potion \
    --to=rkrcmar@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox