1. 21 Apr, 2017 1 commit
    • David Hildenbrand's avatar
      KVM: VMX: drop vmm_exclusive module parameter · fe0e80be
      David Hildenbrand authored
      vmm_exclusive=0 leads to KVM setting X86_CR4_VMXE always and calling
      VMXON only when the vcpu is loaded. X86_CR4_VMXE is used as an
      indication in cpu_emergency_vmxoff() (called on kdump) if VMXOFF has to be
      called. This is obviously not the case if both are used independtly.
      Calling VMXOFF without a previous VMXON will result in an exception.
      
      In addition, X86_CR4_VMXE is used as a mean to test if VMX is already in
      use by another VMM in hardware_enable(). So there can't really be
      co-existance. If the other VMM is prepared for co-existance and does a
      similar check, only one VMM can exist. If the other VMM is not prepared
      and blindly sets/clears X86_CR4_VMXE, we will get inconsistencies with
      X86_CR4_VMXE.
      
      As we also had bug reports related to clearing of vmcs with vmm_exclusive=0
      this seems to be pretty much untested. So let's better drop it.
      
      While at it, directly move setting/clearing X86_CR4_VMXE into
      kvm_cpu_vmxon/off.
      Signed-off-by: default avatarDavid Hildenbrand <david@redhat.com>
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      fe0e80be
  2. 13 Apr, 2017 1 commit
    • Radim Krčmář's avatar
      KVM: nVMX: fix AD condition when handling EPT violation · 33251870
      Radim Krčmář authored
      I have introduced this bug when applying and simplifying Paolo's patch
      as we agreed on the list.  The original was "x &= ~y; if (z) x |= y;".
      
      Here is the story of a bad workflow:
      
        A maintainer was already testing with the intended change, but it was
        applied only to a testing repo on a different machine.  When the time
        to push tested patches to kvm/next came, he realized that this change
        was missing and quickly added it to the maintenance repo, didn't test
        again (because the change is trivial, right), and pushed the world to
        fire.
      
      Fixes: ae1e2d10 ("kvm: nVMX: support EPT accessed/dirty bits")
      Signed-off-by: default avatarRadim Krčmář <rkrcmar@redhat.com>
      33251870
  3. 12 Apr, 2017 28 commits
  4. 11 Apr, 2017 1 commit
    • Radim Krčmář's avatar
      Merge tag 'kvm-s390-next-4.12-1' of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux · f7b1a77d
      Radim Krčmář authored
      From: Christian Borntraeger <borntraeger@de.ibm.com>
      
      KVM: s390: features for 4.12
      
      1. guarded storage support for guests
         This contains an s390 base Linux feature branch that is necessary
         to implement the KVM part
      2. Provide an interface to implement adapter interruption suppression
         which is necessary for proper zPCI support
      3. Use more defines instead of numbers
      4. Provide logging for lazy enablement of runtime instrumentation
      f7b1a77d
  5. 07 Apr, 2017 9 commits