lkml.org 
[lkml]   [2009]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    Date
    From
    Subject[patch 19/71] KVM: take mmu_lock when updating a deleted slot

    2.6.30-stable review patch. If anyone has any objections, please let us know.

    ------------------
    From: Marcelo Tosatti <mtosatti@redhat.com>

    (cherry picked from commit b43b1901ad282aeb74161837fb403927102687a1)

    kvm_handle_hva relies on mmu_lock protection to safely access
    the memslot structures.

    Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
    Signed-off-by: Avi Kivity <avi@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    ---
    virt/kvm/kvm_main.c | 2 ++
    1 file changed, 2 insertions(+)

    --- a/virt/kvm/kvm_main.c
    +++ b/virt/kvm/kvm_main.c
    @@ -1055,8 +1055,10 @@ int __kvm_set_memory_region(struct kvm *

    kvm_free_physmem_slot(&old, npages ? &new : NULL);
    /* Slot deletion case: we have to update the current slot */
    + spin_lock(&kvm->mmu_lock);
    if (!npages)
    *memslot = old;
    + spin_unlock(&kvm->mmu_lock);
    #ifdef CONFIG_DMAR
    /* map the pages in iommu page table */
    r = kvm_iommu_map_pages(kvm, base_gfn, npages);



    \
     
     \ /
      Last update: 2009-09-05 02:57    [W:0.021 / U:30.352 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site