From: Baolu Lu <baolu.lu@linux.intel.com>
To: Vasant Hegde <vasant.hegde@amd.com>,
iommu@lists.linux.dev, joro@8bytes.org
Cc: baolu.lu@linux.intel.com, will@kernel.org, robin.murphy@arm.com,
suravee.suthikulpanit@amd.com, jgg@ziepe.ca, yi.l.liu@intel.com,
kevin.tian@intel.com, jacob.pan@linux.microsoft.com,
Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: [PATCH v3 11/12] iommu: Put domain allocation in __iommu_group_alloc_blocking_domain()
Date: Fri, 18 Oct 2024 12:02:17 +0800 [thread overview]
Message-ID: <0b898ef2-5c1e-4ebc-8f9c-944f64027524@linux.intel.com> (raw)
In-Reply-To: <20241017140137.6028-12-vasant.hegde@amd.com>
On 2024/10/17 22:01, Vasant Hegde wrote:
> From: Jason Gunthorpe<jgg@nvidia.com>
>
> There is no longer a reason to call __iommu_domain_alloc() to allocate
> the blocking domain. All drivers that support a native blocking domain
> provide it via the ops, for other drivers we should call
> iommu_paging_domain_alloc().
>
> __iommu_group_alloc_blocking_domain() is the only place that allocates
> an BLOCKED domain, so move the ops->blocked_domain logic there.
>
> Signed-off-by: Jason Gunthorpe<jgg@nvidia.com>
> Signed-off-by: Vasant Hegde<vasant.hegde@amd.com>
> ---
> drivers/iommu/iommu.c | 25 +++++++++++++------------
> 1 file changed, 13 insertions(+), 12 deletions(-)
Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
Thanks,
baolu
next prev parent reply other threads:[~2024-10-18 4:02 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
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 [this message]
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=0b898ef2-5c1e-4ebc-8f9c-944f64027524@linux.intel.com \
--to=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 \
--cc=yi.l.liu@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