The patch titled
KVM: AMD SVM: Add missing tlb flushes to the guest mmu
has been removed from the -mm tree. Its filename was
kvm-amd-svm-add-missing-tlb-flushes-to-the-guest-mmu.patch
This patch was dropped because it was folded into kvm-userspace-interface.patch
------------------------------------------------------
Subject: KVM: AMD SVM: Add missing tlb flushes to the guest mmu
From: Avi Kivity <avi@xxxxxxxxxxxx>
Add a couple of missing mmu flushes. The Intel tlb is too coarse to be
affected, but they are necessary for AMD.
Signed-off-by: Yaniv Kamay <yaniv@xxxxxxxxxxxx>
Signed-off-by: Avi Kivity <avi@xxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
drivers/kvm/mmu.c | 2 ++
1 files changed, 2 insertions(+)
diff -puN drivers/kvm/mmu.c~kvm-amd-svm-add-missing-tlb-flushes-to-the-guest-mmu drivers/kvm/mmu.c
--- a/drivers/kvm/mmu.c~kvm-amd-svm-add-missing-tlb-flushes-to-the-guest-mmu
+++ a/drivers/kvm/mmu.c
@@ -324,6 +324,7 @@ static void nonpaging_flush(struct kvm_v
if (is_paging(vcpu))
root |= (vcpu->cr3 & (CR3_PCD_MASK | CR3_WPT_MASK));
kvm_arch_ops->set_cr3(vcpu, root);
+ kvm_arch_ops->flush_tlb(vcpu);
}
static gpa_t nonpaging_gva_to_gpa(struct kvm_vcpu *vcpu, gva_t vaddr)
@@ -407,6 +408,7 @@ static void kvm_mmu_flush_tlb(struct kvm
release_pt_page_64(vcpu, page->page_hpa, 1);
}
++kvm_stat.tlb_flush;
+ kvm_arch_ops->flush_tlb(vcpu);
}
static void paging_new_cr3(struct kvm_vcpu *vcpu)
_
Patches currently in -mm which might be from avi@xxxxxxxxxxxx are
origin.patch
kvm-userspace-interface.patch
kvm-amd-svm-add-missing-tlb-flushes-to-the-guest-mmu.patch
kvm-amd-svm-add-data-structures.patch
kvm-amd-svm-implementation.patch
kvm-amd-svm-implementation-avoid-three-more-new-instructions.patch
kvm-amd-svm-implementation-more-i386-fixes.patch
kvm-amd-svm-implementation-printk-log-levels.patch
kvm-amd-svm-plumbing.patch
kvm-fix-null-and-c99-init-sparse-warnings.patch
kvm-load-i386-segment-bases.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
