KVM: MMU: improve write flooding detected

Browse source

Detecting write-flooding does not work well, when we handle page written, if
the last speculative spte is not accessed, we treat the page is
write-flooding, however, we can speculative spte on many path, such as pte
prefetch, page synced, that means the last speculative spte may be not point
to the written page and the written page can be accessed via other sptes, so
depends on the Accessed bit of the last speculative spte is not enough

Instead of detected page accessed, we can detect whether the spte is accessed
after it is written, if the spte is not accessed but it is written frequently,
we treat is not a page table or it not used for a long time

Signed-off-by: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Signed-off-by: Avi Kivity <avi@redhat.com>

...

This commit is contained in:

Xiao Guangrong 2011-09-22 16:58:36 +08:00 • committed by Avi Kivity

parent 5d9ca30e96

commit a30f47cb15

3 changed files with 32 additions and 48 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

6

arch/x86/include/asm/kvm_host.h

View file

62

arch/x86/kvm/mmu.c

View file

12

arch/x86/kvm/paging_tmpl.h

View file