All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Matlack <dmatlack@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Sean Christopherson <seanjc@google.com>
Cc: David Matlack <dmatlack@google.com>,
	Ben Gardon <bgardon@google.com>,
	kvm@vger.kernel.org, Vipin Sharma <vipinsh@google.com>
Subject: [PATCH 0/3] KVM: Performance and correctness fixes for CLEAR_DIRTY_LOG
Date: Fri, 27 Oct 2023 10:26:37 -0700	[thread overview]
Message-ID: <20231027172640.2335197-1-dmatlack@google.com> (raw)

This series reduces the impact of CLEAR_DIRTY_LOG on guest performance
(Patch 3) and fixes 2 minor bugs found along the way (Patches 1 and 2).

We've observed that guest performance can drop while userspace is
issuing CLEAR_DIRTY_LOG ioctls and tracked down the problem to
contention on the mmu_lock in vCPU threads. CLEAR_DIRTY_LOG holds the
write-lock, so this isn't that surprising. We previously explored
converting CLEAR_DIRTY_LOG to hold the read-lock [1], but that has some
negative consequences:

 - Pretty significant code churn is required on x86 and ARM to support
   doing CLEAR under the read-lock. Things get especially hairy on x86
   when considering how to support the Shadow MMU.

 - Holding the read-lock means KVM will have to use atomic
   compare-and-exchange operations during eager splitting and clearing
   dirty bits, which can be quite slow on certain ARM platforms.

This series proposed an alternative (well, complimentary, really)
approach of simply dropping mmu_lock more frequently. I tested this
series out with one of our internal Live Migration tests where the guest
is running MySQL in a 160 vCPU VM (Intel Broadwell host) and it
eliminates the performance drops we were seeing when userspace issues
CLEAR ioctls. Furthermore I don't see any noticeable improvement when I
test with this series plus a prototype patch convert CLEAR to the read
lock on x86. i.e. It seems we can eliminate most of the lock contention
by just dropping the lock more frequently.

Cc: Vipin Sharma <vipinsh@google.com>

[1] https://lore.kernel.org/kvm/20230602160914.4011728-1-vipinsh@google.com/

David Matlack (3):
  KVM: x86/mmu: Fix off-by-1 when splitting huge pages during CLEAR
  KVM: x86/mmu: Check for leaf SPTE when clearing dirty bit in the TDP
    MMU
  KVM: Aggressively drop and reacquire mmu_lock during CLEAR_DIRTY_LOG

 arch/x86/kvm/mmu/mmu.c     | 2 +-
 arch/x86/kvm/mmu/tdp_mmu.c | 7 ++++---
 virt/kvm/kvm_main.c        | 4 ++--
 3 files changed, 7 insertions(+), 6 deletions(-)


base-commit: 2b3f2325e71f09098723727d665e2e8003d455dc
-- 
2.42.0.820.g83a721a137-goog


             reply	other threads:[~2023-10-27 17:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27 17:26 David Matlack [this message]
2023-10-27 17:26 ` [PATCH 1/3] KVM: x86/mmu: Fix off-by-1 when splitting huge pages during CLEAR David Matlack
2023-10-27 17:26 ` [PATCH 2/3] KVM: x86/mmu: Check for leaf SPTE when clearing dirty bit in the TDP MMU David Matlack
2023-10-27 17:26 ` [PATCH 3/3] KVM: Aggressively drop and reacquire mmu_lock during CLEAR_DIRTY_LOG David Matlack
2023-11-08  0:05 ` [PATCH 0/3] KVM: Performance and correctness fixes for CLEAR_DIRTY_LOG Sean Christopherson
2023-11-08  0:23   ` David Matlack
2023-12-01  1:52 ` Sean Christopherson
2023-12-01 15:59   ` 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=20231027172640.2335197-1-dmatlack@google.com \
    --to=dmatlack@google.com \
    --cc=bgardon@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=vipinsh@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.