All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@redhat.com>
To: Tushar Dave <tdave@nvidia.com>,
	alex@shazbot.org, qemu-devel@nongnu.org, skolothumtho@nvidia.com
Cc: jgg@nvidia.com
Subject: Re: [PATCH 1/1] hw/vfio: thread vf-token through iommufd bind
Date: Fri, 11 Sep 2026 07:50:16 +0200	[thread overview]
Message-ID: <81385deb-6cc0-4637-85f1-90db1111ec71@redhat.com> (raw)
In-Reply-To: <20260908160731.1658621-1-tdave@nvidia.com>

On 9/8/26 18:07, Tushar Dave wrote:
> A VF fails to bind through the iommufd/cdev backend when its PF is
> bound to vfio-pci and requires a matching VF token.
> 
> QEMU currently initializes struct vfio_device_bind_iommufd without
> the token flag or token UUID.
> 
> Pass the existing vf-token device property to the IOMMUFD bind ioctl
> for PCI devices.
> 
> Signed-off-by: Tushar Dave <tdave@nvidia.com>
> ---
>   hw/vfio/iommufd.c | 10 ++++++++++
>   1 file changed, 10 insertions(+)
> 
> diff --git a/hw/vfio/iommufd.c b/hw/vfio/iommufd.c
> index 242644aa00..de482128bf 100644
> --- a/hw/vfio/iommufd.c
> +++ b/hw/vfio/iommufd.c
> @@ -155,6 +155,7 @@ static void iommufd_cdev_kvm_device_del(VFIODevice *vbasedev)
>   
>   static bool iommufd_cdev_connect_and_bind(VFIODevice *vbasedev, Error **errp)
>   {
> +    VFIOPCIDevice *vdev = vfio_pci_from_vfio_device(vbasedev);
>       IOMMUFDBackend *iommufd = vbasedev->iommufd;
>       struct vfio_device_bind_iommufd bind = {
>           .argsz = sizeof(bind),
> @@ -180,6 +181,15 @@ static bool iommufd_cdev_connect_and_bind(VFIODevice *vbasedev, Error **errp)
>   
>       /* Bind device to iommufd */
>       bind.iommufd = iommufd->fd;
> +
> +    /*
> +     * Pass the VF token when binding a PCI device.
> +     */
> +    if (vdev && !qemu_uuid_is_null(&vdev->vf_token)) {
> +        bind.flags |= VFIO_DEVICE_BIND_FLAG_TOKEN;
> +        bind.token_uuid_ptr = (uintptr_t)&vdev->vf_token;
> +    }
> +
>       if (ioctl(vbasedev->fd, VFIO_DEVICE_BIND_IOMMUFD, &bind)) {
>           error_setg_errno(errp, errno, "error bind device fd=%d to iommufd=%d",
>                            vbasedev->fd, bind.iommufd);

Reviewed-by: Cédric Le Goater <clg@redhat.com>

Thanks,

C.



  reply	other threads:[~2026-09-11  5:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 16:07 [PATCH 1/1] hw/vfio: thread vf-token through iommufd bind Tushar Dave
2026-09-11  5:50 ` Cédric Le Goater [this message]
2026-09-11  8:12 ` Shameer Kolothum Thodi

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=81385deb-6cc0-4637-85f1-90db1111ec71@redhat.com \
    --to=clg@redhat.com \
    --cc=alex@shazbot.org \
    --cc=jgg@nvidia.com \
    --cc=qemu-devel@nongnu.org \
    --cc=skolothumtho@nvidia.com \
    --cc=tdave@nvidia.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.