public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Keir Fraser <keirf@google.com>
Cc: 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 v3 0/4] KVM: Speed up MMIO registrations
Date: Mon, 8 Sep 2025 12:52:22 -0700	[thread overview]
Message-ID: <aL8z9vZOAeQvTBKF@google.com> (raw)
In-Reply-To: <20250819090853.3988626-1-keirf@google.com>

On Tue, Aug 19, 2025, Keir Fraser wrote:
> This is version 3 of the patches I previously posted here:
> 
>  https://lore.kernel.org/all/20250716110737.2513665-1-keirf@google.com/
> 
> Changes since v2:
> 
>  * Rebased to v6.17-rc2

Note, looks like you missed a tested tag from Li on patch 4:

https://lkml.kernel.org/r/b778c98abb4b425186bfeb1f9bed0c7a%40baidu.com

Nits aside, this looks good to my eyes (though I haven't tested yet).

Marc/Oliver,

Can you weigh in on the vgic changes when you get a chance?  And a more expert
set of eyeballs on the memory ordering side of things would be nice to have, too :-)

As for landing this, I'd be happy to take this through a dedicated kvm-x86 topic
branch, or I can provide an ack on patches 3 and 4 (there's basically zero chance
of this causing a conflict in x86).

> Keir Fraser (4):
>   KVM: arm64: vgic-init: Remove vgic_ready() macro
>   KVM: arm64: vgic: Explicitly implement vgic_dist::ready ordering
>   KVM: Implement barriers before accessing kvm->buses[] on SRCU read
>     paths
>   KVM: Avoid synchronize_srcu() in kvm_io_bus_register_dev()
> 
>  arch/arm64/kvm/vgic/vgic-init.c | 14 +++--------
>  arch/x86/kvm/vmx/vmx.c          |  7 ++++++
>  include/kvm/arm_vgic.h          |  1 -
>  include/linux/kvm_host.h        | 11 ++++++---
>  virt/kvm/kvm_main.c             | 43 +++++++++++++++++++++++++++------
>  5 files changed, 53 insertions(+), 23 deletions(-)
> 
> -- 
> 2.51.0.rc1.193.gad69d77794-goog
> 

      parent reply	other threads:[~2025-09-08 19:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-19  9:08 [PATCH v3 0/4] KVM: Speed up MMIO registrations Keir Fraser
2025-08-19  9:08 ` [PATCH v3 1/4] KVM: arm64: vgic-init: Remove vgic_ready() macro Keir Fraser
2025-08-19  9:08 ` [PATCH v3 2/4] KVM: arm64: vgic: Explicitly implement vgic_dist::ready ordering Keir Fraser
2025-08-19  9:08 ` [PATCH v3 3/4] KVM: Implement barriers before accessing kvm->buses[] on SRCU read paths Keir Fraser
2025-09-08 19:46   ` Sean Christopherson
2025-08-19  9:08 ` [PATCH v3 4/4] KVM: Avoid synchronize_srcu() in kvm_io_bus_register_dev() Keir Fraser
2025-09-08 19:44   ` Sean Christopherson
2025-08-19 14:45 ` [syzbot ci] Re: KVM: Speed up MMIO registrations syzbot ci
2025-09-08 19:52 ` Sean Christopherson [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=aL8z9vZOAeQvTBKF@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 \
    /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