From: Sean Christopherson <seanjc@google.com>
To: Keir Fraser <keirf@google.com>
Cc: Yao Yuan <yaoyuan@linux.alibaba.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Eric Auger <eric.auger@redhat.com>,
Oliver Upton <oliver.upton@linux.dev>,
Marc Zyngier <maz@kernel.org>, Will Deacon <will@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2 2/4] KVM: arm64: vgic: Explicitly implement vgic_dist::ready ordering
Date: Fri, 18 Jul 2025 08:01:41 -0700 [thread overview]
Message-ID: <aHph1ZeYRhWIMCMm@google.com> (raw)
In-Reply-To: <aHpf9vuRK691J7HD@google.com>
On Fri, Jul 18, 2025, Keir Fraser wrote:
> On Thu, Jul 17, 2025 at 01:44:48PM +0800, Yao Yuan wrote:
> > On Wed, Jul 16, 2025 at 11:07:35AM +0800, Keir Fraser wrote:
> > > In preparation to remove synchronize_srcu() from MMIO registration,
> > > remove the distributor's dependency on this implicit barrier by
> > > direct acquire-release synchronization on the flag write and its
> > > lock-free check.
> > >
> > > Signed-off-by: Keir Fraser <keirf@google.com>
> > > ---
> > > arch/arm64/kvm/vgic/vgic-init.c | 11 ++---------
> > > 1 file changed, 2 insertions(+), 9 deletions(-)
> > >
> > > diff --git a/arch/arm64/kvm/vgic/vgic-init.c b/arch/arm64/kvm/vgic/vgic-init.c
> > > index 502b65049703..bc83672e461b 100644
> > > --- a/arch/arm64/kvm/vgic/vgic-init.c
> > > +++ b/arch/arm64/kvm/vgic/vgic-init.c
> > > @@ -567,7 +567,7 @@ int kvm_vgic_map_resources(struct kvm *kvm)
> > > gpa_t dist_base;
> > > int ret = 0;
> > >
> > > - if (likely(dist->ready))
> > > + if (likely(smp_load_acquire(&dist->ready)))
> > > return 0;
> > >
> > > mutex_lock(&kvm->slots_lock);
> > > @@ -598,14 +598,7 @@ int kvm_vgic_map_resources(struct kvm *kvm)
> > > goto out_slots;
> > > }
> > >
> > > - /*
> > > - * kvm_io_bus_register_dev() guarantees all readers see the new MMIO
> > > - * registration before returning through synchronize_srcu(), which also
> > > - * implies a full memory barrier. As such, marking the distributor as
> > > - * 'ready' here is guaranteed to be ordered after all vCPUs having seen
> > > - * a completely configured distributor.
> > > - */
> > > - dist->ready = true;
> > > + smp_store_release(&dist->ready, true);
> >
> > No need the store-release and load-acquire for replacing
> > synchronize_srcu_expedited() w/ call_srcu() IIUC:
> >
> > Tree SRCU on SMP:
> > call_srcu()
> > __call_srcu()
> > srcu_gp_start_if_needed()
> > __srcu_read_unlock_nmisafe()
> > #ifdef CONFIG_NEED_SRCU_NMI_SAFE
> > smp_mb__before_atomic() // __smp_mb() on ARM64, do nothing on x86.
> > #else
> > __srcu_read_unlock()
> > smp_mb()
> > #endif
>
> I don't think it's nice to depend on an implementation detail of
> kvm_io_bus_register_dev() and, transitively, on implementation details
> of call_srcu().
>
> kvm_vgic_map_resources() isn't called that often and can afford its
> own synchronization.
+1
next prev parent reply other threads:[~2025-07-18 15:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 11:07 [PATCH v2 0/4] KVM: Speed up MMIO registrations Keir Fraser
2025-07-16 11:07 ` [PATCH v2 1/4] KVM: arm64: vgic-init: Remove vgic_ready() macro Keir Fraser
2025-07-16 11:07 ` [PATCH v2 2/4] KVM: arm64: vgic: Explicitly implement vgic_dist::ready ordering Keir Fraser
2025-07-17 5:44 ` Yao Yuan
2025-07-18 14:53 ` Keir Fraser
2025-07-18 15:01 ` Sean Christopherson [this message]
2025-07-18 15:25 ` Keir Fraser
2025-07-19 2:23 ` Yao Yuan
2025-07-18 15:00 ` Sean Christopherson
2025-07-19 2:15 ` Yao Yuan
2025-07-19 7:58 ` Keir Fraser
2025-07-20 0:08 ` Yao Yuan
2025-07-21 7:49 ` Keir Fraser
2025-07-22 2:01 ` Yao Yuan
2025-07-22 2:22 ` Yao Yuan
2025-07-16 11:07 ` [PATCH v2 3/4] KVM: Implement barriers before accessing kvm->buses[] on SRCU read paths Keir Fraser
2025-07-17 6:01 ` Yao Yuan
2025-07-18 14:54 ` Sean Christopherson
2025-07-19 2:37 ` Yao Yuan
2025-07-18 14:56 ` Keir Fraser
2025-07-19 2:33 ` Yao Yuan
2025-07-16 11:07 ` [PATCH v2 4/4] KVM: Avoid synchronize_srcu() in kvm_io_bus_register_dev() Keir Fraser
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=aHph1ZeYRhWIMCMm@google.com \
--to=seanjc@google.com \
--cc=eric.auger@redhat.com \
--cc=keirf@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=will@kernel.org \
--cc=yaoyuan@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).