summaryrefslogtreecommitdiffstats
path: root/arch/x86/include/asm
diff options
context:
space:
mode:
authorJunaid Shahid <junaids@google.com>2021-10-20 03:06:27 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2021-10-22 11:19:28 +0200
commit4dfe4f40d845cdca655b27bf207959855f3e2d62 (patch)
tree552cf71e45bec2a7bf0ce07519e5d10b3e75f236 /arch/x86/include/asm
parentKVM: vPMU: Fill get_msr MSR_CORE_PERF_GLOBAL_OVF_CTRL w/ 0 (diff)
downloadlinux-4dfe4f40d845cdca655b27bf207959855f3e2d62.tar.xz
linux-4dfe4f40d845cdca655b27bf207959855f3e2d62.zip
kvm: x86: mmu: Make NX huge page recovery period configurable
Currently, the NX huge page recovery thread wakes up every minute and zaps 1/nx_huge_pages_recovery_ratio of the total number of split NX huge pages at a time. This is intended to ensure that only a relatively small number of pages get zapped at a time. But for very large VMs (or more specifically, VMs with a large number of executable pages), a period of 1 minute could still result in this number being too high (unless the ratio is changed significantly, but that can result in split pages lingering on for too long). This change makes the period configurable instead of fixing it at 1 minute. Users of large VMs can then adjust the period and/or the ratio to reduce the number of pages zapped at one time while still maintaining the same overall duration for cycling through the entire list. By default, KVM derives a period from the ratio such that a page will remain on the list for 1 hour on average. Signed-off-by: Junaid Shahid <junaids@google.com> Message-Id: <20211020010627.305925-1-junaids@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/x86/include/asm')
0 files changed, 0 insertions, 0 deletions