From: David Matlack <dmatlack@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>,
kvm@vger.kernel.org, David Matlack <dmatlack@google.com>
Subject: [PATCH 0/2] KVM: x86/mmu: Do not recover NX Huge Pages when dirty logging is enabled
Date: Thu, 27 Oct 2022 13:03:14 -0700 [thread overview]
Message-ID: <20221027200316.2221027-1-dmatlack@google.com> (raw)
This series turns off the NX Huge Page recovery worker when any memslot
has dirty logging enabled. This avoids theoretical performance problems
and reduces the CPU usage of NX Huge Pages when a VM is in the pre-copy
phase of a Live Migration.
Tested manually and ran all selftests.
David Matlack (2):
KVM: Keep track of the number of memslots with dirty logging enabled
KVM: x86/mmu: Do not recover NX Huge Pages when dirty logging is
enabled
arch/x86/kvm/mmu/mmu.c | 8 ++++++++
include/linux/kvm_host.h | 2 ++
virt/kvm/kvm_main.c | 10 ++++++++++
3 files changed, 20 insertions(+)
base-commit: e18d6152ff0f41b7f01f9817372022df04e0d354
--
2.38.1.273.g43a17bfeac-goog
next reply other threads:[~2022-10-27 20:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 20:03 David Matlack [this message]
2022-10-27 20:03 ` [PATCH 1/2] KVM: Keep track of the number of memslots with dirty logging enabled David Matlack
2022-10-27 20:34 ` Sean Christopherson
2022-10-27 22:15 ` David Matlack
2022-10-27 23:04 ` Sean Christopherson
2022-10-27 20:03 ` [PATCH 2/2] KVM: x86/mmu: Do not recover NX Huge Pages when dirty logging is enabled David Matlack
2022-10-28 10:58 ` [PATCH 0/2] " Paolo Bonzini
2022-10-28 20:05 ` David Matlack
2022-10-28 21:07 ` Sean Christopherson
2022-10-28 21:24 ` David Matlack
2022-10-28 21:42 ` Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221027200316.2221027-1-dmatlack@google.com \
--to=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.