All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Steffen Eiden" <seiden@linux.ibm.com>
Cc: "Christian Borntraeger" <borntraeger@linux.ibm.com>,
	kvm@vger.kernel.org, "Alexander Gordeev" <agordeev@linux.ibm.com>,
	linux-s390@vger.kernel.org, "Heiko Carstens" <hca@linux.ibm.com>,
	"Vasily Gorbik" <gor@linux.ibm.com>
Subject: Re: [PATCH v4 4/6] KVM/vfio: Use file-based reference counting for KVM
Date: Mon, 28 Sep 2026 13:22:33 +0000	[thread overview]
Message-ID: <20260928132233.C63B91F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260928-vfio-v4-4-e32e226d5932@linux.ibm.com>

> Replace manual module reference counting with file-based reference
> counting for KVM integration. Previously, VFIO used symbol_get() to
> obtain function pointers for kvm_get_kvm_safe() and kvm_put_kvm(),
> then manually tracked module references through these symbols. This
> approach required storing the put_kvm function pointer in each device
> and carefully managing symbol references.
> 
> Pass struct file pointers instead of struct kvm pointers throughout the
> VFIO-KVM interface, leveraging the kernel's existing file reference
> counting via get_file()/get_file_active() and fput(). Convert the x86
> page-track API and update s390 vfio to use file_to_kvm_<arch>(). This
> simplifies the code.
> 
> Suggested-by: Jason Gunthorpe <jgg@nvidia.com>
> Co-developed-by: Sean Christopherson <seanjc@google.com>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> Signed-off-by: Steffen Eiden <seiden@linux.ibm.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260928-vfio-v4-0-e32e226d5932@linux.ibm.com?part=4


  reply	other threads:[~2026-09-28 13:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 13:07 [PATCH v4 0/6] KVM/vfio: Use file-based reference counting for KVM Steffen Eiden
2026-09-28 13:07 ` [PATCH v4 1/6] KVM: Introduce file_to_kvm_<arch>() infrastructure Steffen Eiden
2026-09-28 13:14   ` sashiko-bot
2026-09-28 13:07 ` [PATCH v4 2/6] KVM: Add file back-pointer to struct kvm Steffen Eiden
2026-09-28 13:18   ` sashiko-bot
2026-09-28 13:07 ` [PATCH v4 3/6] KVM: x86: Use file_to_kvm_x86() in SEV Steffen Eiden
2026-09-28 13:13   ` sashiko-bot
2026-09-28 13:07 ` [PATCH v4 4/6] KVM/vfio: Use file-based reference counting for KVM Steffen Eiden
2026-09-28 13:22   ` sashiko-bot [this message]
2026-09-29 17:59   ` Claudio Imbrenda
2026-09-30  7:35     ` Steffen Eiden
2026-10-01 17:39   ` Alex Williamson
2026-09-28 13:07 ` [PATCH v4 5/6] KVM: Restrict kvm_get_kvm/kvm_put_kvm export to internal KVM modules Steffen Eiden
2026-09-28 13:12   ` sashiko-bot
2026-09-28 13:07 ` [PATCH v4 6/6] KVM: Remove unused file_is_kvm Steffen Eiden
2026-09-28 13:11   ` sashiko-bot
2026-09-28 19:26 ` [PATCH v4 0/6] KVM/vfio: Use file-based reference counting for KVM Sean Christopherson
2026-09-29 13:05 ` Janosch Frank
2026-09-30  7:45 ` Claudio Imbrenda
2026-10-01 11:59 ` Christian Borntraeger
2026-10-01 17:46   ` Alex Williamson
2026-10-02  8:48     ` Christian Borntraeger
2026-10-07 12:31       ` Christian Borntraeger

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=20260928132233.C63B91F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=seiden@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.