public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Alex Williamson <alex@shazbot.org>
Cc: "Carlos López" <clopez@suse.de>,
	kvm@vger.kernel.org, alex.williamson@redhat.com,
	pbonzini@redhat.com
Subject: Re: [PATCH 0/4] KVM: VFIO: use mutex guards to simplify control flow
Date: Fri, 3 Apr 2026 16:38:10 -0700	[thread overview]
Message-ID: <adBPYqunQxc1CujB@google.com> (raw)
In-Reply-To: <20260318143112.4ac13424@shazbot.org>

On Wed, Mar 18, 2026, Alex Williamson wrote:
> On Fri, 13 Mar 2026 13:20:38 +0100
> Carlos López <clopez@suse.de> wrote:
> 
> > Replace several uses of mutex_lock() / mutex_unlock() pairs with mutex
> > guards, allowing removal of all gotos in virt/kvm/vfio.c.
> > 
> > In this series I also include a small refactor that allows greatly
> > simplifying kvm_vfio_file_del(), and skipping an unnecessary call to
> > kvm_vfio_update_coherency() if the list of files managed by the KVM
> > VFIO device does not change.
> > 
> > Carlos López (4):
> >   KVM: VFIO: clean up control flow in kvm_vfio_file_add()
> >   KVM: VFIO: use mutex guard in kvm_vfio_file_set_spapr_tce()
> >   KVM: VFIO: deduplicate file release logic
> >   KVM: VFIO: update coherency only if file was deleted
> > 
> >  virt/kvm/vfio.c | 97 ++++++++++++++++++-------------------------------
> >  1 file changed, 35 insertions(+), 62 deletions(-)
> > 
> > 
> > base-commit: d2ea4ff1ce50787a98a3900b3fb1636f3620b7cf
> 
> Series looks good to me.  This is nicely isolated, so I assume Paolo
> will take it through the KVM tree, but I can also take it through vfio
> if preferred.

I'll grab it for 7.2, probably around 7.1-rc2.

      reply	other threads:[~2026-04-03 23:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 12:20 [PATCH 0/4] KVM: VFIO: use mutex guards to simplify control flow Carlos López
2026-03-13 12:20 ` [PATCH 1/4] KVM: VFIO: clean up control flow in kvm_vfio_file_add() Carlos López
2026-03-13 12:20 ` [PATCH 2/4] KVM: VFIO: use mutex guard in kvm_vfio_file_set_spapr_tce() Carlos López
2026-04-07  3:48   ` kernel test robot
2026-03-13 12:20 ` [PATCH 3/4] KVM: VFIO: deduplicate file release logic Carlos López
2026-03-13 12:20 ` [PATCH 4/4] KVM: VFIO: update coherency only if file was deleted Carlos López
2026-03-18 20:31 ` [PATCH 0/4] KVM: VFIO: use mutex guards to simplify control flow Alex Williamson
2026-04-03 23:38   ` 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=adBPYqunQxc1CujB@google.com \
    --to=seanjc@google.com \
    --cc=alex.williamson@redhat.com \
    --cc=alex@shazbot.org \
    --cc=clopez@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.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