On Tue, Aug 24, 2010 at 10:31:07AM +0800, Xiaotian Feng wrote: > Latest kvm mmu_shrink code rework makes kernel changes > kvm->arch.n_used_mmu_pages/ > kvm->arch.n_max_mmu_pages at kvm_mmu_free_page/kvm_mmu_alloc_page, which is > called > by kvm_mmu_commit_zap_page. So the kvm->arch.n_used_mmu_pages or > kvm_mmu_available_pages(vcpu->kvm) is unchanged after > kvm_mmu_prepare_zap_page(), > This caused kvm_mmu_change_mmu_pages/__kvm_mmu_free_some_pages loops forever. > Moving kvm_mmu_commit_zap_page would make the while loop performs as normal. > > Reported-by: Avi Kivity <[email protected]> > Signed-off-by: Xiaotian Feng <[email protected]> > Tested-by: Avi Kivity <[email protected]> > Cc: Marcelo Tosatti <[email protected]> > Cc: Dave Hansen <[email protected]> > Cc: Tim Pepper <[email protected]> > --- > arch/x86/kvm/mmu.c | 7 +++---- > 1 files changed, 3 insertions(+), 4 deletions(-)
Applied, thanks. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
