From: Marc Zyngier <maz@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Keir Fraser <keirf@google.com>
Cc: Sean Christopherson <seanjc@google.com>,
Eric Auger <eric.auger@redhat.com>,
Oliver Upton <oliver.upton@linux.dev>,
Will Deacon <will@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v4 0/4] KVM: Speed up MMIO registrations
Date: Mon, 15 Sep 2025 10:59:45 +0100 [thread overview]
Message-ID: <175793036859.521995.4956413640156757969.b4-ty@kernel.org> (raw)
In-Reply-To: <20250909100007.3136249-1-keirf@google.com>
On Tue, 09 Sep 2025 10:00:03 +0000, Keir Fraser wrote:
> This is version 4 of the patches I previously posted here:
>
> https://lore.kernel.org/all/20250819090853.3988626-1-keirf@google.com/
>
> Changes since v3:
>
> * Rebased to v6.17-rc5
> * Added Tested-by tag to patch 4
> * Fixed reproducible syzkaller splat
> * Tweaked comments to Sean's specification
>
> [...]
Applied to next, thanks!
[1/4] KVM: arm64: vgic-init: Remove vgic_ready() macro
commit: 8810c6e7cca8fbfce7652b53e05acc465e671d28
[2/4] KVM: arm64: vgic: Explicitly implement vgic_dist::ready ordering
commit: 11490b5ec6bc4fe3a36f90817bbc8021ba8b05cd
[3/4] KVM: Implement barriers before accessing kvm->buses[] on SRCU read paths
commit: 7788255aba6545a27b8d143c5256536f8dfb2c0a
[4/4] KVM: Avoid synchronize_srcu() in kvm_io_bus_register_dev()
commit: 7d9a0273c45962e9a6bc06f3b87eef7c431c1853
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2025-09-15 9:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 10:00 Keir Fraser
2025-09-09 10:00 ` [PATCH v4 1/4] KVM: arm64: vgic-init: Remove vgic_ready() macro Keir Fraser
2025-09-09 10:00 ` [PATCH v4 2/4] KVM: arm64: vgic: Explicitly implement vgic_dist::ready ordering Keir Fraser
2025-09-09 10:00 ` [PATCH v4 3/4] KVM: Implement barriers before accessing kvm->buses[] on SRCU read paths Keir Fraser
2025-09-09 10:00 ` [PATCH v4 4/4] KVM: Avoid synchronize_srcu() in kvm_io_bus_register_dev() Keir Fraser
2026-02-13 15:42 ` Nikita Kalyazin
2026-02-13 23:20 ` Sean Christopherson
2026-02-16 17:53 ` Nikita Kalyazin
2026-02-17 19:07 ` Sean Christopherson
2026-02-18 12:55 ` Nikita Kalyazin
2026-02-18 16:02 ` Keir Fraser
2026-02-18 16:15 ` Nikita Kalyazin
2026-02-19 7:50 ` Keir Fraser
2026-02-19 11:02 ` Nikita Kalyazin
2025-09-15 9:59 ` Marc Zyngier [this message]
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=175793036859.521995.4956413640156757969.b4-ty@kernel.org \
--to=maz@kernel.org \
--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=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=will@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®