From: Yi Liu <yi.l.liu@intel.com>
To: Vasant Hegde <vasant.hegde@amd.com>, <iommu@lists.linux.dev>,
<joro@8bytes.org>
Cc: <will@kernel.org>, <robin.murphy@arm.com>,
<suravee.suthikulpanit@amd.com>, <jgg@ziepe.ca>,
<baolu.lu@linux.intel.com>, <kevin.tian@intel.com>,
<jacob.pan@linux.microsoft.com>, Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: [PATCH v3 02/12] iommu: Introduce iommu_paging_domain_alloc_flags()
Date: Mon, 21 Oct 2024 15:47:17 +0800 [thread overview]
Message-ID: <942e7019-a477-496c-b04f-b0fb12283187@intel.com> (raw)
In-Reply-To: <20241017140137.6028-3-vasant.hegde@amd.com>
On 2024/10/17 22:01, Vasant Hegde wrote:
> From: Jason Gunthorpe <jgg@ziepe.ca>
>
> Currently drivers calls iommu_paging_domain_alloc(dev) to get an
> UNMANAGED domain. This is not sufficient to support PASID with
> UNMANAGED domain as some HW like AMD requires certain page table type
> to support PASIDs.
>
> Also domain_alloc_paging() passes device as param for domain
The below may look clearer to reader. :)
"Also the domain_alloc_paging op only passes device as param for domain"
> allocation. This is not sufficient for AMD driver to decide the right
> page table.
> > Hence add iommu_paging_domain_alloc_flags() API which takes flags as
> parameter. Driver can pass additional parameter to indicate type of
> domain required, etc. iommu_paging_domain_alloc_flags() internally calls
> appropriate callback function to allocate a domain.
how about mentioning that the domain_alloc_user op accepts flags from
user which meets the AMD driver's requirement? Hence, it's clear why
we are not extending the domain_alloc_paging op to accept flags. :)
>
> Signed-off-by: Jason Gunthorpe <jgg@ziepe.ca>
> [Added description - Vasant]
> Signed-off-by: Vasant Hegde <vasant.hegde@amd.com>
> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
> ---
> drivers/iommu/iommu.c | 30 ++++++++++++++++++++++++++----
> include/linux/iommu.h | 14 +++++++++++---
> 2 files changed, 37 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> index 811748bec4b0..e13d64ffd14f 100644
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@ -2027,20 +2027,42 @@ struct iommu_domain *iommu_domain_alloc(const struct bus_type *bus)
> EXPORT_SYMBOL_GPL(iommu_domain_alloc);
>
> /**
> - * iommu_paging_domain_alloc() - Allocate a paging domain
> + * iommu_paging_domain_alloc_flags() - Allocate a paging domain
> * @dev: device for which the domain is allocated
> + * @flags: Bitmap of iommufd_hwpt_alloc_flags
maybe "enum iommufd_hwpt_alloc_flags" would be more accurate.
> *
> * Allocate a paging domain which will be managed by a kernel driver. Return
> * allocated domain if successful, or a ERR pointer for failure.
nit: s/a/an/
with above minor comments, this patch LGTM.
Reviewed-by: Yi Liu <yi.l.liu@intel.com>
> */
> -struct iommu_domain *iommu_paging_domain_alloc(struct device *dev)
> +struct iommu_domain *iommu_paging_domain_alloc_flags(struct device *dev,
> + unsigned int flags)
> {
> + const struct iommu_ops *ops;
> + struct iommu_domain *domain;
> +
> if (!dev_has_iommu(dev))
> return ERR_PTR(-ENODEV);
>
> - return __iommu_domain_alloc(dev_iommu_ops(dev), dev, IOMMU_DOMAIN_UNMANAGED);
> + ops = dev_iommu_ops(dev);
> +
> + if (ops->domain_alloc_paging && !flags)
> + domain = ops->domain_alloc_paging(dev);
> + else if (ops->domain_alloc_user)
> + domain = ops->domain_alloc_user(dev, flags, NULL, NULL);
> + else if (ops->domain_alloc && !flags)
> + domain = ops->domain_alloc(IOMMU_DOMAIN_UNMANAGED);
> + else
> + return ERR_PTR(-EOPNOTSUPP);
> +
> + if (IS_ERR(domain))
> + return domain;
> + if (!domain)
> + return ERR_PTR(-ENOMEM);
> +
> + iommu_domain_init(domain, IOMMU_DOMAIN_UNMANAGED, ops);
> + return domain;
> }
> -EXPORT_SYMBOL_GPL(iommu_paging_domain_alloc);
> +EXPORT_SYMBOL_GPL(iommu_paging_domain_alloc_flags);
>
> void iommu_domain_free(struct iommu_domain *domain)
> {
> diff --git a/include/linux/iommu.h b/include/linux/iommu.h
> index bd722f473635..42243183e81d 100644
> --- a/include/linux/iommu.h
> +++ b/include/linux/iommu.h
> @@ -511,8 +511,6 @@ static inline int __iommu_copy_struct_from_user_array(
> * the caller iommu_domain_alloc() returns.
> * @domain_alloc_user: Allocate an iommu domain corresponding to the input
> * parameters as defined in include/uapi/linux/iommufd.h.
> - * Unlike @domain_alloc, it is called only by IOMMUFD and
> - * must fully initialize the new domain before return.
> * Upon success, if the @user_data is valid and the @parent
> * points to a kernel-managed domain, the new domain must be
> * IOMMU_DOMAIN_NESTED type; otherwise, the @parent must be
> @@ -789,7 +787,11 @@ extern bool iommu_present(const struct bus_type *bus);
> extern bool device_iommu_capable(struct device *dev, enum iommu_cap cap);
> extern bool iommu_group_has_isolated_msi(struct iommu_group *group);
> extern struct iommu_domain *iommu_domain_alloc(const struct bus_type *bus);
> -struct iommu_domain *iommu_paging_domain_alloc(struct device *dev);
> +struct iommu_domain *iommu_paging_domain_alloc_flags(struct device *dev, unsigned int flags);
> +static inline struct iommu_domain *iommu_paging_domain_alloc(struct device *dev)
> +{
> + return iommu_paging_domain_alloc_flags(dev, 0);
> +}
> extern void iommu_domain_free(struct iommu_domain *domain);
> extern int iommu_attach_device(struct iommu_domain *domain,
> struct device *dev);
> @@ -1096,6 +1098,12 @@ static inline struct iommu_domain *iommu_domain_alloc(const struct bus_type *bus
> return NULL;
> }
>
> +struct iommu_domain *iommu_paging_domain_alloc_flags(struct device *dev,
> + unsigned int flags)
> +{
> + return ERR_PTR(-ENODEV);
> +}
> +
> static inline struct iommu_domain *iommu_paging_domain_alloc(struct device *dev)
> {
> return ERR_PTR(-ENODEV);
--
Regards,
Yi Liu
next prev parent reply other threads:[~2024-10-21 7:42 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 14:01 [PATCH v3 00/12] iommu: Domain allocation enhancements Vasant Hegde
2024-10-17 14:01 ` [PATCH v3 01/12] iommu: Refactor __iommu_domain_alloc() Vasant Hegde
2024-10-21 7:29 ` Yi Liu
2024-10-21 9:10 ` Vasant Hegde
2024-10-17 14:01 ` [PATCH v3 02/12] iommu: Introduce iommu_paging_domain_alloc_flags() Vasant Hegde
2024-10-18 3:29 ` Baolu Lu
2024-10-21 7:47 ` Yi Liu [this message]
2024-10-21 9:19 ` Vasant Hegde
2024-10-17 14:01 ` [PATCH v3 03/12] iommu: Add new flag to explictly request PASID capable domain Vasant Hegde
2024-10-18 3:43 ` Baolu Lu
2024-10-18 12:43 ` Jason Gunthorpe
2024-10-21 5:02 ` Baolu Lu
2024-10-18 14:16 ` Jason Gunthorpe
2024-10-21 10:02 ` Vasant Hegde
2024-10-21 7:57 ` Yi Liu
2024-10-23 8:52 ` Vasant Hegde
2024-10-21 7:59 ` Yi Liu
2024-10-22 4:54 ` Vasant Hegde
2024-10-17 14:01 ` [PATCH v3 04/12] iommu/arm-smmu-v3: Enhance domain_alloc_user() to allocate " Vasant Hegde
2024-10-18 14:23 ` Jason Gunthorpe
2024-10-21 8:57 ` Vasant Hegde
2024-10-17 14:01 ` [PATCH v3 05/12] iommu/amd: Add helper function to check GIOSUP/GTSUP Vasant Hegde
2024-10-18 14:23 ` Jason Gunthorpe
2024-10-17 14:01 ` [PATCH v3 06/12] iommu/amd: Move V2 page table support check to early_amd_iommu_init() Vasant Hegde
2024-10-18 14:24 ` Jason Gunthorpe
2024-10-17 14:01 ` [PATCH v3 07/12] iommu/amd: Separate page table setup from domain allocation Vasant Hegde
2024-10-17 14:01 ` [PATCH v3 08/12] iommu/amd: Pass page table type as param to pdom_setup_pgtable() Vasant Hegde
2024-10-18 14:25 ` Jason Gunthorpe
2024-10-17 14:01 ` [PATCH v3 09/12] iommu/amd: Enhance amd_iommu_domain_alloc_user() Vasant Hegde
2024-10-18 14:27 ` Jason Gunthorpe
2024-10-21 9:00 ` Vasant Hegde
2024-10-22 7:48 ` Tian, Kevin
2024-10-23 8:47 ` Vasant Hegde
2024-10-17 14:01 ` [PATCH v3 10/12] iommu/amd: Implement global identity domain Vasant Hegde
2024-10-17 14:01 ` [PATCH v3 11/12] iommu: Put domain allocation in __iommu_group_alloc_blocking_domain() Vasant Hegde
2024-10-18 4:02 ` Baolu Lu
2024-10-17 14:01 ` [PATCH v3 12/12] iommu: Create __iommu_alloc_identity_domain() Vasant Hegde
2024-10-18 4:04 ` Baolu Lu
2024-10-18 14:32 ` Jason Gunthorpe
2024-10-21 6:38 ` Vasant Hegde
2024-10-18 3:10 ` [PATCH v3 00/12] iommu: Domain allocation enhancements Baolu Lu
2024-10-18 12:50 ` Jason Gunthorpe
2024-10-21 9:08 ` Vasant Hegde
2024-10-22 7:50 ` Tian, Kevin
2024-10-23 8:48 ` Vasant Hegde
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=942e7019-a477-496c-b04f-b0fb12283187@intel.com \
--to=yi.l.liu@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jacob.pan@linux.microsoft.com \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.com \
--cc=will@kernel.org \
/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