1. 15 2月, 2009 4 次提交
    • S
      KVM: Add kvm_arch_sync_events to sync with asynchronize events · ad8ba2cd
      Sheng Yang 提交于
      kvm_arch_sync_events is introduced to quiet down all other events may happen
      contemporary with VM destroy process, like IRQ handler and work struct for
      assigned device.
      
      For kvm_arch_sync_events is called at the very beginning of kvm_destroy_vm(), so
      the state of KVM here is legal and can provide a environment to quiet down other
      events.
      Signed-off-by: NSheng Yang <sheng@linux.intel.com>
      Signed-off-by: NAvi Kivity <avi@redhat.com>
      ad8ba2cd
    • M
      KVM: mmu_notifiers release method · 85db06e5
      Marcelo Tosatti 提交于
      The destructor for huge pages uses the backing inode for adjusting
      hugetlbfs accounting.
      
      Hugepage mappings are destroyed by exit_mmap, after
      mmu_notifier_release, so there are no notifications through
      unmap_hugepage_range at this point.
      
      The hugetlbfs inode can be freed with pages backed by it referenced
      by the shadow. When the shadow releases its reference, the huge page
      destructor will access a now freed inode.
      
      Implement the release operation for kvm mmu notifiers to release page
      refs before the hugetlbfs inode is gone.
      Signed-off-by: NMarcelo Tosatti <mtosatti@redhat.com>
      Signed-off-by: NAvi Kivity <avi@redhat.com>
      85db06e5
    • A
      KVM: Avoid using CONFIG_ in userspace visible headers · 7a0eb196
      Avi Kivity 提交于
      Kconfig symbols are not available in userspace, and are not stripped by
      headers-install.  Avoid their use by adding #defines in <asm/kvm.h> to
      suit each architecture.
      Signed-off-by: NAvi Kivity <avi@redhat.com>
      7a0eb196
    • Y
      KVM: ia64: fix fp fault/trap handler · d39123a4
      Yang Zhang 提交于
      The floating-point registers f6-f11 is used by vmm and
      saved in kvm-pt-regs, so should set the correct bit mask
      and the pointer in fp_state, otherwise, fpswa may touch
      vmm's fp registers instead of guests'.
      
      In addition, for fp trap handling,  since the instruction
      which leads to fp trap is completely executed, so can't
      use retry machanism to re-execute it, because it may
      pollute some registers.
      Signed-off-by: NYang Zhang <yang.zhang@intel.com>
      Signed-off-by: NAvi Kivity <avi@redhat.com>
      d39123a4
  2. 14 2月, 2009 3 次提交
  3. 13 2月, 2009 32 次提交
  4. 12 2月, 2009 1 次提交