diff options
| author | Makarand Sonare <makarandsonare@google.com> | 2021-02-13 01:50:12 +0100 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2021-02-19 09:08:34 +0100 |
| commit | a85863c2ec55edcfd11853014b143fc02b8840a9 (patch) | |
| tree | c7772a30d1067c14656659f5d6abb9a9e033eaf1 /arch/x86/include/asm/user_32.h | |
| parent | KVM: x86: Further clarify the logic and comments for toggling log dirty (diff) | |
| download | linux-a85863c2ec55edcfd11853014b143fc02b8840a9.tar.xz linux-a85863c2ec55edcfd11853014b143fc02b8840a9.zip | |
KVM: VMX: Dynamically enable/disable PML based on memslot dirty logging
Currently, if enable_pml=1 PML remains enabled for the entire lifetime
of the VM irrespective of whether dirty logging is enable or disabled.
When dirty logging is disabled, all the pages of the VM are manually
marked dirty, so that PML is effectively non-operational. Setting
the dirty bits is an expensive operation which can cause severe MMU
lock contention in a performance sensitive path when dirty logging is
disabled after a failed or canceled live migration.
Manually setting dirty bits also fails to prevent PML activity if some
code path clears dirty bits, which can incur unnecessary VM-Exits.
In order to avoid this extra overhead, dynamically enable/disable PML
when dirty logging gets turned on/off for the first/last memslot.
Signed-off-by: Makarand Sonare <makarandsonare@google.com>
Co-developed-by: Sean Christopherson <seanjc@google.com>
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20210213005015.1651772-12-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/x86/include/asm/user_32.h')
0 files changed, 0 insertions, 0 deletions