1. 16 Apr, 2013 5 commits
  2. 14 Apr, 2013 5 commits
  3. 08 Apr, 2013 2 commits
  4. 07 Apr, 2013 1 commit
  5. 20 Mar, 2013 1 commit
  6. 18 Mar, 2013 1 commit
  7. 14 Mar, 2013 2 commits
  8. 13 Mar, 2013 2 commits
    • Jan Kiszka's avatar
      KVM: nVMX: Clean up and fix pin-based execution controls · eabeaacc
      Jan Kiszka authored
      
      
      Only interrupt and NMI exiting are mandatory for KVM to work, thus can
      be exposed to the guest unconditionally, virtual NMI exiting is
      optional. So we must not advertise it unless the host supports it.
      
      Introduce the symbolic constant PIN_BASED_ALWAYSON_WITHOUT_TRUE_MSR at
      this chance.
      
      Reviewed-by: default avatar: Paolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: default avatarGleb Natapov <gleb@redhat.com>
      eabeaacc
    • Jan Kiszka's avatar
      KVM: x86: Rework INIT and SIPI handling · 66450a21
      Jan Kiszka authored
      
      
      A VCPU sending INIT or SIPI to some other VCPU races for setting the
      remote VCPU's mp_state. When we were unlucky, KVM_MP_STATE_INIT_RECEIVED
      was overwritten by kvm_emulate_halt and, thus, got lost.
      
      This introduces APIC events for those two signals, keeping them in
      kvm_apic until kvm_apic_accept_events is run over the target vcpu
      context. kvm_apic_has_events reports to kvm_arch_vcpu_runnable if there
      are pending events, thus if vcpu blocking should end.
      
      The patch comes with the side effect of effectively obsoleting
      KVM_MP_STATE_SIPI_RECEIVED. We still accept it from user space, but
      immediately translate it to KVM_MP_STATE_INIT_RECEIVED + KVM_APIC_SIPI.
      The vcpu itself will no longer enter the KVM_MP_STATE_SIPI_RECEIVED
      state. That also means we no longer exit to user space after receiving a
      SIPI event.
      
      Furthermore, we already reset the VCPU on INIT, only fixing up the code
      segment later on when SIPI arrives. Moreover, we fix INIT handling for
      the BSP: it never enter wait-for-SIPI but directly starts over on INIT.
      
      Tested-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: default avatarGleb Natapov <gleb@redhat.com>
      66450a21
  9. 12 Mar, 2013 1 commit
  10. 11 Mar, 2013 1 commit
  11. 07 Mar, 2013 2 commits
  12. 05 Mar, 2013 2 commits
  13. 04 Mar, 2013 1 commit
  14. 28 Feb, 2013 2 commits
  15. 27 Feb, 2013 4 commits
  16. 22 Feb, 2013 2 commits
  17. 14 Feb, 2013 1 commit
  18. 11 Feb, 2013 1 commit
  19. 07 Feb, 2013 1 commit
  20. 06 Feb, 2013 1 commit
  21. 29 Jan, 2013 2 commits