From: Sean Christopherson <seanjc@google.com>
To: Marco Elver <elver@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Kiryl Shutsemau <kas@kernel.org>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
David Hildenbrand <david@kernel.org>,
kvm@vger.kernel.org, linux-coco@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 04/10] KVM: Refactor kvm_handle_hva_range() to avoid conditional mmu_lock
Date: Thu, 10 Sep 2026 09:38:36 -0700 [thread overview]
Message-ID: <aqLdDIGPaclTYpjU@google.com> (raw)
In-Reply-To: <20260910162343.4092060-5-elver@google.com>
On Thu, Sep 10, 2026, Marco Elver wrote:
> Refactor kvm_handle_hva_range() to check for overlapping memslots
> upfront via interval_tree_iter_first() instead of tracking found
> memslots inside the range iteration with a 'found_memslot' flag and
> conditionally acquiring and releasing mmu_lock.
>
> This simplifies the control flow by cleanly decoupling the search for
> overlapping memslots from the subsequent walk. It also separates the
> lockless path from the serialized path into distinct branches,
> eliminating the conditional locking, which subsequently enables Clang
> context analysis to validate locking in this function.
At the cost of duplicating code and adding overhead when there is a relevant
memslot. I'm not wedded to the exact implementation, but IMO this is not at all
an improvement. Without a clear explanation of what value is added by enabling
Clang to "validate locking", I don't see any justificatoin for the change.
> No functional change intended.
>
> Signed-off-by: Marco Elver <elver@google.com>
> ---
> virt/kvm/kvm_main.c | 94 ++++++++++++++++++++++++++++-----------------
> 1 file changed, 58 insertions(+), 36 deletions(-)
>
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index 65eb26a0520d..f7bfa2d32507 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -558,31 +558,14 @@ static void kvm_null_fn(void)
> node; \
> node = interval_tree_iter_next(node, start, last)) \
>
> -static __always_inline kvm_mn_ret_t kvm_handle_hva_range(struct kvm *kvm,
> - const struct kvm_mmu_notifier_range *range)
> +static __always_inline bool __kvm_handle_hva_range_walk(struct kvm *kvm,
> + const struct kvm_mmu_notifier_range *range)
> {
> - struct kvm_mmu_notifier_return r = {
> - .ret = false,
> - .found_memslot = false,
> - };
> struct kvm_gfn_range gfn_range;
> struct kvm_memory_slot *slot;
> struct kvm_memslots *slots;
> - int i, idx;
> -
> - if (WARN_ON_ONCE(range->end <= range->start))
> - return r;
> -
> - /* A null handler is allowed if and only if on_lock() is provided. */
> - if (WARN_ON_ONCE(IS_KVM_NULL_FN(range->on_lock) &&
> - IS_KVM_NULL_FN(range->handler)))
> - return r;
> -
> - /* on_lock will never be called for lockless walks */
> - if (WARN_ON_ONCE(range->lockless && !IS_KVM_NULL_FN(range->on_lock)))
> - return r;
> -
> - idx = srcu_read_lock(&kvm->srcu);
> + bool ret = false;
> + int i;
>
> for (i = 0; i < kvm_arch_nr_memslot_as_ids(kvm); i++) {
> struct interval_tree_node *node;
> @@ -620,28 +603,67 @@ static __always_inline kvm_mn_ret_t kvm_handle_hva_range(struct kvm *kvm,
> gfn_range.slot = slot;
> gfn_range.lockless = range->lockless;
>
> - if (!r.found_memslot) {
> - r.found_memslot = true;
> - if (!range->lockless) {
> - KVM_MMU_LOCK(kvm);
> - if (!IS_KVM_NULL_FN(range->on_lock))
> - range->on_lock(kvm);
> + ret |= range->handler(kvm, &gfn_range);
> + }
> + }
> +
> + return ret;
> +}
>
> - if (IS_KVM_NULL_FN(range->handler))
> - goto mmu_unlock;
> - }
> - }
> - r.ret |= range->handler(kvm, &gfn_range);
> +static __always_inline kvm_mn_ret_t kvm_handle_hva_range(struct kvm *kvm,
> + const struct kvm_mmu_notifier_range *range)
> +{
> + struct kvm_mmu_notifier_return r = {
> + .ret = false,
> + .found_memslot = false,
> + };
> + struct kvm_memslots *slots;
> + int i, idx;
> +
> + if (WARN_ON_ONCE(range->end <= range->start))
> + return r;
> +
> + /* A null handler is allowed if and only if on_lock() is provided. */
> + if (WARN_ON_ONCE(IS_KVM_NULL_FN(range->on_lock) &&
> + IS_KVM_NULL_FN(range->handler)))
> + return r;
> +
> + /* on_lock will never be called for lockless walks */
> + if (WARN_ON_ONCE(range->lockless && !IS_KVM_NULL_FN(range->on_lock)))
> + return r;
> +
> + idx = srcu_read_lock(&kvm->srcu);
> +
> + for (i = 0; i < kvm_arch_nr_memslot_as_ids(kvm); i++) {
> + slots = __kvm_memslots(kvm, i);
> + if (interval_tree_iter_first(&slots->hva_tree, range->start, range->end - 1)) {
> + r.found_memslot = true;
> + break;
> }
> }
>
> - if (range->flush_on_ret && r.ret)
> - kvm_flush_remote_tlbs(kvm);
> + if (!r.found_memslot)
> + goto out;
> +
> + if (range->lockless) {
> + r.ret = __kvm_handle_hva_range_walk(kvm, range);
> + if (range->flush_on_ret && r.ret)
> + kvm_flush_remote_tlbs(kvm);
> + } else {
> + KVM_MMU_LOCK(kvm);
> + if (!IS_KVM_NULL_FN(range->on_lock))
> + range->on_lock(kvm);
> +
> + if (!IS_KVM_NULL_FN(range->handler))
> + r.ret = __kvm_handle_hva_range_walk(kvm, range);
> +
> + if (range->flush_on_ret && r.ret)
> + kvm_flush_remote_tlbs(kvm);
>
> -mmu_unlock:
> - if (r.found_memslot && !range->lockless)
> KVM_MMU_UNLOCK(kvm);
> + }
>
> +out:
> srcu_read_unlock(&kvm->srcu, idx);
>
> return r;
> --
> 2.55.0.1003.g10538fe699-goog
>
next prev parent reply other threads:[~2026-09-10 16:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 16:21 [PATCH RFC 00/10] KVM: Enable Clang Context Analysis Marco Elver
2026-09-10 16:21 ` [PATCH RFC 01/10] KVM: x86/pmu: Acquire SRCU in pmc_is_event_allowed() to protect filter lookup Marco Elver
2026-09-10 16:46 ` Sean Christopherson
2026-09-10 16:21 ` [PATCH RFC 02/10] KVM: Allow reading memslots while holding slots_arch_lock Marco Elver
2026-09-10 16:30 ` Sean Christopherson
2026-09-10 17:11 ` Marco Elver
2026-09-10 17:52 ` Sean Christopherson
2026-09-10 19:05 ` Marco Elver
2026-09-10 16:21 ` [PATCH RFC 03/10] KVM: guest_memfd: Avoid conditional mmu_lock acquisition Marco Elver
2026-09-10 16:21 ` [PATCH RFC 04/10] KVM: Refactor kvm_handle_hva_range() to avoid conditional mmu_lock Marco Elver
2026-09-10 16:38 ` Sean Christopherson [this message]
2026-09-10 16:21 ` [PATCH RFC 05/10] KVM: Refactor kvm_handle_gfn_range() " Marco Elver
2026-09-10 16:21 ` [PATCH RFC 06/10] KVM: Add basic lock context annotations Marco Elver
2026-09-10 16:21 ` [PATCH RFC 07/10] KVM: x86: " Marco Elver
2026-09-10 16:21 ` [PATCH RFC 08/10] KVM: Add guarded_by to members in struct kvm Marco Elver
2026-09-10 16:21 ` [PATCH RFC 09/10] KVM: x86: Add guarded_by annotations for kvm_arch, kvm_hv, and ioapic Marco Elver
2026-09-10 16:21 ` [PATCH RFC 10/10] KVM: x86: Enable CONTEXT_ANALYSIS with opt-outs Marco Elver
2026-09-10 16:55 ` [PATCH RFC 00/10] KVM: Enable Clang Context Analysis Sean Christopherson
2026-09-10 19:19 ` Marco Elver
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=aqLdDIGPaclTYpjU@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=elver@google.com \
--cc=hpa@zytor.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=tglx@kernel.org \
--cc=vkuznets@redhat.com \
--cc=x86@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®