From: Jason Gunthorpe <jgg@nvidia.com>
To: Yi Liu <yi.l.liu@intel.com>
Cc: joro@8bytes.org, alex.williamson@redhat.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
Subject: Re: [PATCH v6 3/4] iommufd: Add IOMMU_GET_HW_INFO
Date: Wed, 9 Aug 2023 13:43:33 -0300 [thread overview]
Message-ID: <ZNPCNQxUesiMD1wM@nvidia.com> (raw)
In-Reply-To: <20230808153510.4170-4-yi.l.liu@intel.com>
On Tue, Aug 08, 2023 at 08:35:09AM -0700, Yi Liu wrote:
> +static int iommufd_zero_fill_user(void __user *ptr, size_t bytes)
> +{
> + int index = 0;
> +
> + for (; index < bytes; index++) {
> + if (put_user(0, (uint8_t __user *)(ptr + index)))
> + return -EFAULT;
> + }
I've recently learned this routine is spelled 'clear_user()'
Jason
next prev parent reply other threads:[~2023-08-09 16:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 15:35 [PATCH v6 0/4] iommufd: Add iommu hardware info reporting Yi Liu
2023-08-08 15:35 ` [PATCH v6 1/4] iommu: Move dev_iommu_ops() to private header Yi Liu
2023-08-08 15:35 ` [PATCH v6 2/4] iommu: Add new iommu op to get iommu hardware information Yi Liu
2023-08-08 15:35 ` [PATCH v6 3/4] iommufd: Add IOMMU_GET_HW_INFO Yi Liu
2023-08-09 10:16 ` Baolu Lu
2023-08-09 16:16 ` Jason Gunthorpe
2023-08-10 2:05 ` Baolu Lu
2023-08-09 16:43 ` Jason Gunthorpe [this message]
2023-08-10 3:35 ` Liu, Yi L
2023-08-08 15:35 ` [PATCH v6 4/4] iommufd/selftest: Add coverage for IOMMU_GET_HW_INFO ioctl Yi Liu
2023-08-09 16:45 ` Jason Gunthorpe
2023-08-11 6:57 ` Liu, Yi L
2023-08-11 12:01 ` Jason Gunthorpe
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=ZNPCNQxUesiMD1wM@nvidia.com \
--to=jgg@nvidia.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=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=yi.l.liu@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