From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: seanjc@google.com
Subject: [PATCH v2 0/2] KVM: Don't take mmu_lock for range invalidation unless necessary
Date: Tue, 27 Jul 2021 13:18:06 -0400 [thread overview]
Message-ID: <20210727171808.1645060-1-pbonzini@redhat.com> (raw)
This is my take on Sean's patch to restrict taking the mmu_lock in the
MMU notifiers. The first patch includes the locking changes, while
the second is the optimization.
v1->v2: moved the "if (!kvm->mmu_notifier_count)" early return to patch 2
Paolo Bonzini (1):
KVM: Block memslot updates across range_start() and range_end()
Sean Christopherson (1):
KVM: Don't take mmu_lock for range invalidation unless necessary
Documentation/virt/kvm/locking.rst | 6 +++
include/linux/kvm_host.h | 10 +++-
virt/kvm/kvm_main.c | 79 ++++++++++++++++++++++++------
3 files changed, 78 insertions(+), 17 deletions(-)
--
2.27.0
next reply other threads:[~2021-07-27 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 17:18 Paolo Bonzini [this message]
2021-07-27 17:18 ` [PATCH 1/2] KVM: Block memslot updates across range_start() and range_end() Paolo Bonzini
2021-08-02 18:30 ` Sean Christopherson
2021-07-27 17:18 ` [PATCH 2/2] KVM: Don't take mmu_lock for range invalidation unless necessary Paolo Bonzini
2021-08-02 19:05 ` 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=20210727171808.1645060-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.