From: Yi Liu <yi.l.liu@intel.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: <jgg@nvidia.com>, <kevin.tian@intel.com>,
<baolu.lu@linux.intel.com>, <joro@8bytes.org>,
<eric.auger@redhat.com>, <nicolinc@nvidia.com>,
<kvm@vger.kernel.org>, <chao.p.peng@linux.intel.com>,
<iommu@lists.linux.dev>, <zhenzhong.duan@intel.com>,
<vasant.hegde@amd.com>, <will@kernel.org>
Subject: Re: [PATCH v5 3/5] vfio: VFIO_DEVICE_[AT|DE]TACH_IOMMUFD_PT support pasid
Date: Tue, 12 Nov 2024 09:53:29 +0800 [thread overview]
Message-ID: <7cbf3b2f-df84-4277-ae95-54696b0d672c@intel.com> (raw)
In-Reply-To: <20241111170247.01f5314e.alex.williamson@redhat.com>
On 2024/11/12 08:02, Alex Williamson wrote:
> On Fri, 8 Nov 2024 04:17:40 -0800
> Yi Liu <yi.l.liu@intel.com> wrote:
>
>> This extends the VFIO_DEVICE_[AT|DE]TACH_IOMMUFD_PT ioctls to attach/detach
>> 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 | 69 +++++++++++++++++++++++++++++++++-----
>> include/uapi/linux/vfio.h | 29 ++++++++++------
>> 2 files changed, 80 insertions(+), 18 deletions(-)
>>
>> diff --git a/drivers/vfio/device_cdev.c b/drivers/vfio/device_cdev.c
>> index bb1817bd4ff3..4519f482e212 100644
>> --- a/drivers/vfio/device_cdev.c
>> +++ b/drivers/vfio/device_cdev.c
>> @@ -162,9 +162,9 @@ void vfio_df_unbind_iommufd(struct vfio_device_file *df)
>> int vfio_df_ioctl_attach_pt(struct vfio_device_file *df,
>> struct vfio_device_attach_iommufd_pt __user *arg)
>> {
>> - struct vfio_device *device = df->device;
>> struct vfio_device_attach_iommufd_pt attach;
>> - unsigned long minsz;
>> + struct vfio_device *device = df->device;
>> + unsigned long minsz, xend = 0;
>> int ret;
>>
>> minsz = offsetofend(struct vfio_device_attach_iommufd_pt, pt_id);
>> @@ -172,11 +172,38 @@ int vfio_df_ioctl_attach_pt(struct vfio_device_file *df,
>> if (copy_from_user(&attach, arg, minsz))
>> return -EFAULT;
>>
>> - if (attach.argsz < minsz || attach.flags)
>> + if (attach.argsz < minsz)
>> return -EINVAL;
>>
>> + if (attach.flags & (~VFIO_DEVICE_ATTACH_PASID))
>> + return -EINVAL;
>> +
>> + if (attach.flags & VFIO_DEVICE_ATTACH_PASID)
>> + xend = offsetofend(struct vfio_device_attach_iommufd_pt, pasid);
>> +
>> + /*
>> + * xend may be equal to minsz if a flag is defined for reusing a
>> + * reserved field or a special usage of an existing field.
>> + */
>> + if (xend > minsz) {
>> + if (attach.argsz < xend)
>> + return -EINVAL;
>> +
>> + if (copy_from_user((void *)&attach + minsz,
>> + (void __user *)arg + minsz, xend - minsz))
>> + return -EFAULT;
>> + }
>> +
>> + if ((attach.flags & VFIO_DEVICE_ATTACH_PASID) &&
>> + !device->ops->pasid_attach_ioas)
>> + return -EOPNOTSUPP;
>> +
>> mutex_lock(&device->dev_set->lock);
>> - ret = device->ops->attach_ioas(device, &attach.pt_id);
>> + if (attach.flags & VFIO_DEVICE_ATTACH_PASID)
>
> I'd just do the ops test here:
> {
> if (!device->ops->pasid_attach_ios)
> ret = -EOPNOTSUPP;
> else...
>
>> + ret = device->ops->pasid_attach_ioas(device, attach.pasid,
>> + &attach.pt_id);
got it.
> } else {
>
> (Obviously if we weren't about to generalize the prior chunk of code,
> we'd test ops before the 2nd copy_from_user) Thanks,
yes. that's the trade-off for the generalization. :)
--
Regards,
Yi Liu
next prev parent reply other threads:[~2024-11-12 1:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 12:17 [PATCH v5 0/5] vfio-pci support pasid attach/detach Yi Liu
2024-11-08 12:17 ` [PATCH v5 1/5] ida: Add ida_find_first_range() Yi Liu
2024-11-08 12:17 ` [PATCH v5 2/5] vfio-iommufd: Support pasid [at|de]tach for physical VFIO devices Yi Liu
2024-11-08 12:17 ` [PATCH v5 3/5] vfio: VFIO_DEVICE_[AT|DE]TACH_IOMMUFD_PT support pasid Yi Liu
2024-11-12 0:02 ` Alex Williamson
2024-11-12 1:53 ` Yi Liu [this message]
2024-11-08 12:17 ` [PATCH v5 4/5] vfio: Add vfio_copy_user_data() Yi Liu
2024-11-12 0:03 ` Alex Williamson
2024-11-12 9:18 ` Yi Liu
2024-11-12 13:52 ` Alex Williamson
2024-11-13 7:22 ` Yi Liu
2024-11-14 18:19 ` Alex Williamson
2024-11-15 12:10 ` Yi Liu
2024-11-08 12:17 ` [PATCH v5 5/5] iommufd: Extend IOMMU_GET_HW_INFO to report PASID capability Yi Liu
2024-12-11 2:43 ` Zhangfei Gao
2024-12-11 3:12 ` 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=7cbf3b2f-df84-4277-ae95-54696b0d672c@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=eric.auger@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=vasant.hegde@amd.com \
--cc=will@kernel.org \
--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