[GIT PULL] KVM changes for 4.3-rc4

From: Paolo Bonzini
Date: Thu Oct 01 2015 - 14:14:53 EST


Linus,

The following changes since commit 9ffecb10283508260936b96022d4ee43a7798b4c:

Linux 4.3-rc3 (2015-09-27 07:50:08 -0400)

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 d2922422c48df93f3edff7d872ee4f3191fefb08:

Use WARN_ON_ONCE for missing X86_FEATURE_NRIPS (2015-10-01 14:59:37 +0200)

----------------------------------------------------------------
(Relatively) a lot of reverts, mostly.

Bugs have trickled in for a new feature in 4.2 (MTRR support in guests)
so I'm reverting it all; let's not make this -rc period busier for KVM
than it's been so far. This covers the four reverts from me.

The fifth patch is being reverted because Radim found a bug in the
implementation of stable scheduler clock, *but* also managed to implement
the feature entirely without hypervisor support. So instead of fixing
the hypervisor side we can remove it completely; 4.4 will get the new
implementation.

----------------------------------------------------------------
Dirk MÃller (2):
Update KVM homepage Url
Use WARN_ON_ONCE for missing X86_FEATURE_NRIPS

Paolo Bonzini (4):
Revert "KVM: x86: apply guest MTRR virtualization on host reserved pages"
Revert "KVM: SVM: Sync g_pat with guest-written PAT value"
Revert "KVM: svm: handle KVM_X86_QUIRK_CD_NW_CLEARED in svm_get_mt_mask"
Revert "KVM: SVM: use NPT page attributes"

Radim KrÄmÃÅ (1):
Revert "KVM: x86: zero kvmclock_offset when vcpu0 initializes kvmclock system MSR"

MAINTAINERS | 4 +-
arch/x86/include/asm/pvclock-abi.h | 1 +
arch/x86/kvm/svm.c | 125 ++++---------------------------------
arch/x86/kvm/vmx.c | 11 +++-
arch/x86/kvm/x86.c | 4 --
5 files changed, 24 insertions(+), 121 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/