From: Yi Liu <yi.l.liu@intel.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: <joro@8bytes.org>, <jgg@nvidia.com>, <kevin.tian@intel.com>,
<robin.murphy@arm.com>, <baolu.lu@linux.intel.com>,
<cohuck@redhat.com>, <eric.auger@redhat.com>,
<nicolinc@nvidia.com>, <kvm@vger.kernel.org>,
<mjrosato@linux.ibm.com>, <chao.p.peng@linux.intel.com>,
<yi.y.sun@linux.intel.com>, <peterx@redhat.com>,
<jasowang@redhat.com>, <shameerali.kolothum.thodi@huawei.com>,
<lulu@redhat.com>, <suravee.suthikulpanit@amd.com>,
<iommu@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>, <zhenzhong.duan@intel.com>,
<joao.m.martins@oracle.com>, <xin.zeng@intel.com>,
<yan.y.zhao@intel.com>
Subject: Re: [PATCH 2/3] vfio: Add VFIO_DEVICE_PASID_[AT|DE]TACH_IOMMUFD_PT
Date: Tue, 12 Dec 2023 11:02:13 +0800 [thread overview]
Message-ID: <a5bc36fd-dcbe-4b09-b9e3-90578871f776@intel.com> (raw)
In-Reply-To: <20231211100501.1c4032ce.alex.williamson@redhat.com>
On 2023/12/12 01:05, Alex Williamson wrote:
> On Sun, 26 Nov 2023 22:39:08 -0800
> Yi Liu <yi.l.liu@intel.com> wrote:
>
>> This adds ioctls for the userspace to attach a given pasid of a vfio
>> device to/from an IOAS/HWPT.
>>
>> Signed-off-by: Yi Liu <yi.l.liu@intel.com>
>> ---
>> drivers/vfio/device_cdev.c | 45 +++++++++++++++++++++++++++++++
>> drivers/vfio/vfio.h | 4 +++
>> drivers/vfio/vfio_main.c | 8 ++++++
>> include/uapi/linux/vfio.h | 55 ++++++++++++++++++++++++++++++++++++++
>> 4 files changed, 112 insertions(+)
>>
>> diff --git a/drivers/vfio/device_cdev.c b/drivers/vfio/device_cdev.c
>> index e75da0a70d1f..c2ac7ed44537 100644
>> --- a/drivers/vfio/device_cdev.c
>> +++ b/drivers/vfio/device_cdev.c
>> @@ -210,6 +210,51 @@ int vfio_df_ioctl_detach_pt(struct vfio_device_file *df,
>> return 0;
>> }
>>
>> +int vfio_df_ioctl_pasid_attach_pt(struct vfio_device_file *df,
>> + struct vfio_device_pasid_attach_iommufd_pt __user *arg)
>> +{
>> + struct vfio_device *device = df->device;
>> + struct vfio_device_pasid_attach_iommufd_pt attach;
>> + unsigned long minsz;
>> + int ret;
>> +
>> + minsz = offsetofend(struct vfio_device_pasid_attach_iommufd_pt, pt_id);
>> +
>> + if (copy_from_user(&attach, arg, minsz))
>> + return -EFAULT;
>> +
>> + if (attach.argsz < minsz || attach.flags)
>> + return -EINVAL;
>> +
>> + mutex_lock(&device->dev_set->lock);
>> + ret = device->ops->pasid_attach_ioas(device, attach.pasid, &attach.pt_id);
>
> These callbacks were only implemented for vfio-pci in the previous
> patch but they're called unconditionally. Thanks,
yes, will correct it and below. thanks for catching it.
>
> Alex
>
>> + mutex_unlock(&device->dev_set->lock);
>> +
>> + return ret;
>> +}
>> +
>> +int vfio_df_ioctl_pasid_detach_pt(struct vfio_device_file *df,
>> + struct vfio_device_pasid_detach_iommufd_pt __user *arg)
>> +{
>> + struct vfio_device *device = df->device;
>> + struct vfio_device_pasid_detach_iommufd_pt detach;
>> + unsigned long minsz;
>> +
>> + minsz = offsetofend(struct vfio_device_pasid_detach_iommufd_pt, flags);
>> +
>> + if (copy_from_user(&detach, arg, minsz))
>> + return -EFAULT;
>> +
>> + if (detach.argsz < minsz || detach.flags)
>> + return -EINVAL;
>> +
>> + mutex_lock(&device->dev_set->lock);
>> + device->ops->pasid_detach_ioas(device, detach.pasid);
>> + mutex_unlock(&device->dev_set->lock);
>> +
>> + return 0;
>> +}
>> +
>> static char *vfio_device_devnode(const struct device *dev, umode_t *mode)
>> {
>> return kasprintf(GFP_KERNEL, "vfio/devices/%s", dev_name(dev));
>> diff --git a/drivers/vfio/vfio.h b/drivers/vfio/vfio.h
>> index 307e3f29b527..d228cdb6b345 100644
>> --- a/drivers/vfio/vfio.h
>> +++ b/drivers/vfio/vfio.h
>> @@ -353,6 +353,10 @@ int vfio_df_ioctl_attach_pt(struct vfio_device_file *df,
>> struct vfio_device_attach_iommufd_pt __user *arg);
>> int vfio_df_ioctl_detach_pt(struct vfio_device_file *df,
>> struct vfio_device_detach_iommufd_pt __user *arg);
>> +int vfio_df_ioctl_pasid_attach_pt(struct vfio_device_file *df,
>> + struct vfio_device_pasid_attach_iommufd_pt __user *arg);
>> +int vfio_df_ioctl_pasid_detach_pt(struct vfio_device_file *df,
>> + struct vfio_device_pasid_detach_iommufd_pt __user *arg);
>>
>> #if IS_ENABLED(CONFIG_VFIO_DEVICE_CDEV)
>> void vfio_init_device_cdev(struct vfio_device *device);
>> diff --git a/drivers/vfio/vfio_main.c b/drivers/vfio/vfio_main.c
>> index 8d4995ada74a..ff50c239873d 100644
>> --- a/drivers/vfio/vfio_main.c
>> +++ b/drivers/vfio/vfio_main.c
>> @@ -1240,6 +1240,14 @@ static long vfio_device_fops_unl_ioctl(struct file *filep,
>> case VFIO_DEVICE_DETACH_IOMMUFD_PT:
>> ret = vfio_df_ioctl_detach_pt(df, uptr);
>> goto out;
>> +
>> + case VFIO_DEVICE_PASID_ATTACH_IOMMUFD_PT:
>> + ret = vfio_df_ioctl_pasid_attach_pt(df, uptr);
>> + goto out;
>> +
>> + case VFIO_DEVICE_PASID_DETACH_IOMMUFD_PT:
>> + ret = vfio_df_ioctl_pasid_detach_pt(df, uptr);
>> + goto out;
>> }
>> }
>>
>> diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h
>> index 94b3badefde3..495193629029 100644
>> --- a/include/uapi/linux/vfio.h
>> +++ b/include/uapi/linux/vfio.h
>> @@ -977,6 +977,61 @@ struct vfio_device_detach_iommufd_pt {
>>
>> #define VFIO_DEVICE_DETACH_IOMMUFD_PT _IO(VFIO_TYPE, VFIO_BASE + 20)
>>
>> +/*
>> + * VFIO_DEVICE_PASID_ATTACH_IOMMUFD_PT - _IOW(VFIO_TYPE, VFIO_BASE + 21,
>> + * struct vfio_device_pasid_attach_iommufd_pt)
>> + * @argsz: User filled size of this data.
>> + * @flags: Must be 0.
>> + * @pasid: The pasid to be attached.
>> + * @pt_id: Input the target id which can represent an ioas or a hwpt
>> + * allocated via iommufd subsystem.
>> + * Output the input ioas id or the attached hwpt id which could
>> + * be the specified hwpt itself or a hwpt automatically created
>> + * for the specified ioas by kernel during the attachment.
>> + *
>> + * Associate a pasid (of a cdev device) with an address space within the
>> + * bound iommufd. Undo by VFIO_DEVICE_PASID_DETACH_IOMMUFD_PT or device fd
>> + * close. This is only allowed on cdev fds.
>> + *
>> + * If a pasid is currently attached to a valid hw_pagetable (hwpt), without
>> + * doing a VFIO_DEVICE_PASID_DETACH_IOMMUFD_PT, a second
>> + * VFIO_DEVICE_PASID_ATTACH_IOMMUFD_PT ioctl passing in another hwpt id is
>> + * allowed. This action, also known as a hwpt replacement, will replace the
>> + * pasid's currently attached hwpt with a new hwpt corresponding to the given
>> + * @pt_id.
>> + *
>> + * Return: 0 on success, -errno on failure.
>> + */
>> +struct vfio_device_pasid_attach_iommufd_pt {
>> + __u32 argsz;
>> + __u32 flags;
>> + __u32 pasid;
>> + __u32 pt_id;
>> +};
>> +
>> +#define VFIO_DEVICE_PASID_ATTACH_IOMMUFD_PT _IO(VFIO_TYPE, VFIO_BASE + 21)
>> +
>> +/*
>> + * VFIO_DEVICE_PASID_DETACH_IOMMUFD_PT - _IOW(VFIO_TYPE, VFIO_BASE + 22,
>> + * struct vfio_device_pasid_detach_iommufd_pt)
>> + * @argsz: User filled size of this data.
>> + * @flags: Must be 0.
>> + * @pasid: The pasid to be detached.
>> + *
>> + * Remove the association of a pasid (of a cdev device) and its current
>> + * associated address space. After it, the pasid of the device should be in
>> + * a blocking DMA state. This is only allowed on cdev fds.
>> + *
>> + * Return: 0 on success, -errno on failure.
>> + */
>> +struct vfio_device_pasid_detach_iommufd_pt {
>> + __u32 argsz;
>> + __u32 flags;
>> + __u32 pasid;
>> +};
>> +
>> +#define VFIO_DEVICE_PASID_DETACH_IOMMUFD_PT _IO(VFIO_TYPE, VFIO_BASE + 22)
>> +
>> /*
>> * Provide support for setting a PCI VF Token, which is used as a shared
>> * secret between PF and VF drivers. This feature may only be set on a
>
--
Regards,
Yi Liu
next prev parent reply other threads:[~2023-12-12 2:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 6:39 [PATCH 0/3] vfio-pci support pasid attach/detach Yi Liu
2023-11-27 6:39 ` [PATCH 1/3] vfio-iommufd: Support pasid [at|de]tach for physical VFIO devices Yi Liu
2024-01-15 17:18 ` Jason Gunthorpe
2023-11-27 6:39 ` [PATCH 2/3] vfio: Add VFIO_DEVICE_PASID_[AT|DE]TACH_IOMMUFD_PT Yi Liu
2023-11-27 6:50 ` Duan, Zhenzhong
2023-11-28 3:06 ` Yi Liu
2023-12-11 17:05 ` Alex Williamson
2023-12-12 3:02 ` Yi Liu [this message]
2023-11-27 6:39 ` [PATCH 3/3] vfio: Report PASID capability via VFIO_DEVICE_FEATURE ioctl Yi Liu
2023-11-27 7:28 ` Duan, Zhenzhong
2023-11-28 3:11 ` Yi Liu
2023-11-28 4:23 ` Duan, Zhenzhong
2023-12-07 8:47 ` Tian, Kevin
2023-12-11 8:08 ` Yi Liu
2023-12-12 2:20 ` Tian, Kevin
2023-12-12 3:26 ` Yi Liu
2023-12-12 15:31 ` Jason Gunthorpe
2023-12-13 1:59 ` Tian, Kevin
2023-12-11 18:03 ` Alex Williamson
2023-12-11 18:10 ` Jason Gunthorpe
2023-12-11 18:49 ` Alex Williamson
2023-12-12 15:35 ` Jason Gunthorpe
2023-12-13 2:10 ` Tian, Kevin
2024-01-15 9:49 ` Yi Liu
2023-12-12 2:16 ` Tian, Kevin
2023-12-12 3:44 ` Yi Liu
2023-12-12 2:43 ` Duan, Zhenzhong
2023-12-12 3:39 ` Alex Williamson
2023-12-12 3:53 ` Yi Liu
2023-12-12 15:27 ` Jason Gunthorpe
2024-01-15 8:20 ` Yi Liu
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=a5bc36fd-dcbe-4b09-b9e3-90578871f776@intel.com \
--to=yi.l.liu@intel.com \
--cc=alex.williamson@redhat.com \
--cc=baolu.lu@linux.intel.com \
--cc=chao.p.peng@linux.intel.com \
--cc=cohuck@redhat.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=jasowang@redhat.com \
--cc=jgg@nvidia.com \
--cc=joao.m.martins@oracle.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=mjrosato@linux.ibm.com \
--cc=nicolinc@nvidia.com \
--cc=peterx@redhat.com \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=xin.zeng@intel.com \
--cc=yan.y.zhao@intel.com \
--cc=yi.y.sun@linux.intel.com \
--cc=zhenzhong.duan@intel.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