mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Sean Christopherson <seanjc@google.com>
Subject: [GIT PULL] KVM: VFIO changes for 7.2
Date: Thu, 11 Jun 2026 17:47:53 -0700	[thread overview]
Message-ID: <20260612004755.349925-9-seanjc@google.com> (raw)
In-Reply-To: <20260612004755.349925-1-seanjc@google.com>

The following changes since commit b7fbe9a1bf9ee6c967ef77d366ca58c35fcf1887:

  Merge branch 'kvm-apx-prepare' into HEAD (2026-05-13 12:38:31 -0400)

are available in the Git repository at:

  https://github.com/kvm-x86/linux.git tags/kvm-x86-vfio-7.2

for you to fetch changes up to 156615264fd3430e7f90b36f46076b2f6ec4a24a:

  KVM: VFIO: update coherency only if file was deleted (2026-05-13 11:12:40 -0700)

----------------------------------------------------------------
KVM VFIO changes for 7.2

Use guard() to cleanup up various KVM+VFIO flows.

----------------------------------------------------------------
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 | 98 +++++++++++++++++++++------------------------------------
 1 file changed, 35 insertions(+), 63 deletions(-)

  parent reply	other threads:[~2026-06-12  0:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-12  0:47 [GIT PULL] KVM: x86 pull requests " Sean Christopherson
2026-06-12  0:47 ` [GIT PULL] KVM: x86: Generic changes " Sean Christopherson
2026-06-12  8:07   ` Paolo Bonzini
2026-06-12  0:47 ` [GIT PULL] KVM: x86: guest_memfd " Sean Christopherson
2026-06-12  8:10   ` Paolo Bonzini
2026-06-12  0:47 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2026-06-12  8:14   ` Paolo Bonzini
2026-06-12  0:47 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2026-06-12  8:14   ` Paolo Bonzini
2026-06-12  0:47 ` [GIT PULL] KVM: x86: Selftests " Sean Christopherson
2026-06-12  8:12   ` Paolo Bonzini
2026-06-12  0:47 ` [GIT PULL] KVM: x86: SEV " Sean Christopherson
2026-06-12  8:13   ` Paolo Bonzini
2026-06-12  0:47 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2026-06-12  0:47 ` Sean Christopherson [this message]
2026-06-12  8:14   ` [GIT PULL] KVM: VFIO " Paolo Bonzini
2026-06-12  0:47 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
2026-06-12  8:15   ` Paolo Bonzini

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=20260612004755.349925-9-seanjc@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®