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 v4 3/4] iommufd: Add IOMMU_GET_HW_INFO
Date: Mon, 24 Jul 2023 14:50:07 -0300 [thread overview]
Message-ID: <ZL65z0i8d42Try7a@nvidia.com> (raw)
In-Reply-To: <20230724105936.107042-4-yi.l.liu@intel.com>
On Mon, Jul 24, 2023 at 03:59:35AM -0700, Yi Liu wrote:
> diff --git a/drivers/iommu/iommufd/main.c b/drivers/iommu/iommufd/main.c
> index 94c498b8fdf6..bd3efc1d8509 100644
> --- a/drivers/iommu/iommufd/main.c
> +++ b/drivers/iommu/iommufd/main.c
> @@ -17,6 +17,7 @@
> #include <linux/bug.h>
> #include <uapi/linux/iommufd.h>
> #include <linux/iommufd.h>
> +#include "../iommu-priv.h"
>
> #include "io_pagetable.h"
> #include "iommufd_private.h"
> @@ -177,6 +178,78 @@ static int iommufd_destroy(struct iommufd_ucmd *ucmd)
> return 0;
> }
>
> +static int iommufd_zero_fill_user(u64 ptr, int bytes)
(void __user * ptr, size_t bytes)
> +{
> + int index = 0;
> +
> + for (; index < bytes; index++) {
> + if (put_user(0, (uint8_t __user *)u64_to_user_ptr(ptr + index)))
> + return -EFAULT;
> + }
> + return 0;
> +}
> +
> +static int iommufd_get_hw_info(struct iommufd_ucmd *ucmd)
> +{
> + struct iommu_hw_info *cmd = ucmd->cmd;
> + unsigned int length = 0, data_len;
> + struct iommufd_device *idev;
> + const struct iommu_ops *ops;
> + void *data = NULL;
> + int rc = 0;
> +
> + if (cmd->flags || cmd->__reserved || !cmd->data_len)
> + return -EOPNOTSUPP;
> +
> + idev = iommufd_get_device(ucmd, cmd->dev_id);
> + if (IS_ERR(idev))
> + return PTR_ERR(idev);
> +
> + ops = dev_iommu_ops(idev->dev);
> + if (!ops->hw_info)
> + goto done;
> +
> + /* driver has hw_info callback should have a unique hw_info_type */
> + if (WARN_ON_ONCE(ops->hw_info_type == IOMMU_HW_INFO_TYPE_NONE)) {
> + pr_warn_ratelimited("iommu driver set an invalid type\n");
Don't really need both a WARN and pr_warn(), just keep the WARN_ON
Jason
next prev parent reply other threads:[~2023-07-24 17:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 10:59 [PATCH v4 0/4] iommufd: Add iommu hardware info reporting Yi Liu
2023-07-24 10:59 ` [PATCH v4 1/4] iommu: Move dev_iommu_ops() to private header Yi Liu
2023-07-24 17:43 ` Jason Gunthorpe
2023-07-24 10:59 ` [PATCH v4 2/4] iommu: Add new iommu op to get iommu hardware information Yi Liu
2023-07-27 7:57 ` Tian, Kevin
2023-07-27 14:43 ` Jason Gunthorpe
2023-07-28 2:05 ` Tian, Kevin
2023-07-31 8:33 ` Liu, Yi L
2023-07-31 13:45 ` Jason Gunthorpe
2023-08-01 3:58 ` Liu, Yi L
2023-07-24 10:59 ` [PATCH v4 3/4] iommufd: Add IOMMU_GET_HW_INFO Yi Liu
2023-07-24 17:50 ` Jason Gunthorpe [this message]
2023-07-31 8:35 ` Liu, Yi L
2023-07-24 10:59 ` [PATCH v4 4/4] iommufd/selftest: Add coverage for IOMMU_GET_HW_INFO ioctl Yi Liu
2023-07-24 17:52 ` Jason Gunthorpe
2023-07-27 8:35 ` Nicolin Chen
2023-07-27 8:14 ` Tian, Kevin
2023-07-27 8:38 ` Nicolin Chen
2023-07-27 9:14 ` Tian, Kevin
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=ZL65z0i8d42Try7a@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;
as well as URLs for NNTP newsgroup(s).