Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Vipin Sharma <vipinsh@google.com>
To: Raghavendra Rao Ananta <rananta@google.com>
Cc: David Matlack <dmatlack@google.com>,
	 Alex Williamson <alex@shazbot.org>,
	Josh Hilke <jrhilke@google.com>,
	kvm@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 7/8] vfio: selftests: Add helpers to alloc/free vfio_pci_device
Date: Tue, 12 May 2026 15:30:23 -0700	[thread overview]
Message-ID: <20260512223013.GG3046123.vipinsh@google.com> (raw)
In-Reply-To: <20260505212838.1698034-8-rananta@google.com>

On Tue, May 05, 2026 at 09:28:37PM +0000, Raghavendra Rao Ananta wrote:
> Add a helper, vfio_pci_device_alloc(), to allocate 'struct
> vfio_pci_device'. The subsequent test patch will utilize this
> to get the struct with very minimal initialization done.
> Internally, let vfio_pci_device_init() also make use of this
> function and later do the full initialization.
> 
> Symmetrically, add a free variant, vfio_pci_device_free(),
> to be used in a similar fashion.
> 
> No functional change intended.
> 
> Signed-off-by: Raghavendra Rao Ananta <rananta@google.com>
> Reviewed-by: David Matlack <dmatlack@google.com>
> ---
>  .../vfio/lib/include/libvfio/vfio_pci_device.h |  2 ++
>  .../selftests/vfio/lib/vfio_pci_device.c       | 18 ++++++++++++++++--
>  2 files changed, 18 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/testing/selftests/vfio/lib/include/libvfio/vfio_pci_device.h b/tools/testing/selftests/vfio/lib/include/libvfio/vfio_pci_device.h
> index 4ebdc00e20fca..3eabead717bbd 100644
> --- a/tools/testing/selftests/vfio/lib/include/libvfio/vfio_pci_device.h
> +++ b/tools/testing/selftests/vfio/lib/include/libvfio/vfio_pci_device.h
> @@ -38,6 +38,8 @@ struct vfio_pci_device {
>  #define dev_info(_dev, _fmt, ...) printf("%s: " _fmt, (_dev)->bdf, ##__VA_ARGS__)
>  #define dev_err(_dev, _fmt, ...) fprintf(stderr, "%s: " _fmt, (_dev)->bdf, ##__VA_ARGS__)
>  
> +struct vfio_pci_device *vfio_pci_device_alloc(const char *bdf, struct iommu *iommu);
> +void vfio_pci_device_free(struct vfio_pci_device *device);
>  struct vfio_pci_device *vfio_pci_device_init(const char *bdf, struct iommu *iommu);
>  void vfio_pci_device_cleanup(struct vfio_pci_device *device);
>  
> diff --git a/tools/testing/selftests/vfio/lib/vfio_pci_device.c b/tools/testing/selftests/vfio/lib/vfio_pci_device.c
> index 6b855fbcb4a22..94dc5fcecbeb6 100644
> --- a/tools/testing/selftests/vfio/lib/vfio_pci_device.c
> +++ b/tools/testing/selftests/vfio/lib/vfio_pci_device.c
> @@ -421,7 +421,7 @@ static void vfio_pci_iommufd_setup(struct vfio_pci_device *device,
>  	vfio_device_attach_iommufd_pt(device->fd, device->iommu->ioas_id);
>  }
>  
> -struct vfio_pci_device *vfio_pci_device_init(const char *bdf, struct iommu *iommu)
> +struct vfio_pci_device *vfio_pci_device_alloc(const char *bdf, struct iommu *iommu)
>  {
>  	struct vfio_pci_device *device;
>  
> @@ -432,6 +432,20 @@ struct vfio_pci_device *vfio_pci_device_init(const char *bdf, struct iommu *iomm
>  	device->iommu = iommu;
>  	device->bdf = bdf;
>  
> +	return device;
> +}
> +
> +void vfio_pci_device_free(struct vfio_pci_device *device)
> +{
> +	free(device);
> +}
> +
> +struct vfio_pci_device *vfio_pci_device_init(const char *bdf, struct iommu *iommu)
> +{
> +	struct vfio_pci_device *device;
> +
> +	device = vfio_pci_device_alloc(bdf, iommu);
> +
>  	if (iommu->mode->container_path)
>  		vfio_pci_container_setup(device, bdf, NULL);
>  	else
> @@ -464,5 +478,5 @@ void vfio_pci_device_cleanup(struct vfio_pci_device *device)
>  	if (device->group_fd)
>  		VFIO_ASSERT_EQ(close(device->group_fd), 0);
>  
> -	free(device);
> +	vfio_pci_device_free(device);
>  }
> -- 
> 2.54.0.545.g6539524ca2-goog
> 
Reviewed-by: Vipin Sharma <vipinsh@google.com> 

  reply	other threads:[~2026-05-12 22:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05 21:28 [PATCH v8 0/8] vfio: selftest: Add SR-IOV UAPI test Raghavendra Rao Ananta
2026-05-05 21:28 ` [PATCH v8 1/8] vfio: selftests: Add -Wall and -Werror to the Makefile Raghavendra Rao Ananta
2026-05-12 22:25   ` Vipin Sharma
2026-05-05 21:28 ` [PATCH v8 2/8] vfio: selftests: Introduce snprintf_assert() Raghavendra Rao Ananta
2026-05-12 22:26   ` Vipin Sharma
2026-05-05 21:28 ` [PATCH v8 3/8] vfio: selftests: Introduce a sysfs lib Raghavendra Rao Ananta
2026-05-12 22:28   ` Vipin Sharma
2026-05-05 21:28 ` [PATCH v8 4/8] vfio: selftests: Extend container/iommufd setup for passing vf_token Raghavendra Rao Ananta
2026-05-12 22:29   ` Vipin Sharma
2026-05-05 21:28 ` [PATCH v8 5/8] vfio: selftests: Expose more vfio_pci_device functions Raghavendra Rao Ananta
2026-05-12 22:29   ` Vipin Sharma
2026-05-05 21:28 ` [PATCH v8 6/8] vfio: selftests: Add helper to set/override a vf_token Raghavendra Rao Ananta
2026-05-12 22:30   ` Vipin Sharma
2026-05-05 21:28 ` [PATCH v8 7/8] vfio: selftests: Add helpers to alloc/free vfio_pci_device Raghavendra Rao Ananta
2026-05-12 22:30   ` Vipin Sharma [this message]
2026-05-05 21:28 ` [PATCH v8 8/8] vfio: selftests: Add tests to validate SR-IOV UAPI Raghavendra Rao Ananta
2026-05-12 22:31   ` Vipin Sharma

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=20260512223013.GG3046123.vipinsh@google.com \
    --to=vipinsh@google.com \
    --cc=alex@shazbot.org \
    --cc=dmatlack@google.com \
    --cc=jrhilke@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rananta@google.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