From: Vasant Hegde <vasant.hegde@amd.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: iommu@lists.linux.dev, joro@8bytes.org, will@kernel.org,
robin.murphy@arm.com, suravee.suthikulpanit@amd.com,
yi.l.liu@intel.com, baolu.lu@linux.intel.com,
kevin.tian@intel.com
Subject: Re: [PATCH 1/5] iommu: Enhance domain allocation code to take additional flags
Date: Thu, 29 Aug 2024 18:04:28 +0530 [thread overview]
Message-ID: <6adbba52-3f61-42e4-8b1c-d90abf3b192d@amd.com> (raw)
In-Reply-To: <20240826135615.GH3468552@ziepe.ca>
Jason,
On 8/26/2024 7:26 PM, Jason Gunthorpe wrote:
> On Mon, Aug 26, 2024 at 02:06:27PM +0530, Vasant Hegde wrote:
>>>> @Jason,
>>>> Notice that I have added __iommu_paging_domain_alloc_flags() so that
>>>> it can call iommu_domain_init() with appropriate domain type.
>>>
>>> It is okay, but also the type could be fixed in
>>> __iommu_group_alloc_default_domain() using something like:
>>>
>>> ret->type |= req_type;
>>
>> Sorry. I didn't get it. You mean domain->type?
>
> Sorry, yes. I mean the path that knows it is allocating for the DMA
> API can or in the DMA API flags after allocation succeeds and we don't
> have to muddle lower levels by passing them all around.
Ok.
>
>>>> I think instead of having separate function it may be better to
>>>> enhance __iommu_domain_alloc() such that:
>>>> - Keep below changes from this patch
>>>> - iommu_domain_init()
>>>> - iommu_get_dma_cookie call inside iommu_setup_default_domain()
>>>> - modify __iommu_domain_alloc() to additional param (flags)
>>>> - iommu_paging_domain_alloc_flags() will call __iommu_domain_alloc()
>>>
>>> My expectation was to basically remove iommu_domain_alloc() entirely
>>> once Lu's work is merged.
>>>
>>> Instead we'd have these direct APIs:
>>> iommu_domain_alloc_paging_flags()
>>> iommu_group_alloc_blocking_domain()
>>> iommu_group_alloc_identity_domain()
>>
>> Sure (For AMD driver, we may have to tweak a bit to allocate_identity domain,
>> but doable).
>
> Why does it need to allocate_identity ?
Ignore. I got mixed up with global identity domain and this one.
>
>>> I think the series looks OK. The naming of domain_alloc_user() is now
>>> a little bit weird, it has now turned into
>>> domain_alloc_paging_extended().
>>
>> Ack. Do you want me to do it now -OR- May be wait until all changes settles down
>> (above described group() related changes, this series, Baolu's series, etc)?
>
> I think if we rename things it will clash with the smmu nesting
> series, lets live with it for now.
Sure.
-Vasant
next prev parent reply other threads:[~2024-08-29 12:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 13:35 [PATCH 0/5] iommu: Domain allocation enhancements Vasant Hegde
2024-08-21 13:35 ` [PATCH 1/5] iommu: Enhance domain allocation code to take additional flags Vasant Hegde
2024-08-21 16:31 ` Jason Gunthorpe
2024-08-22 1:50 ` Baolu Lu
2024-08-22 12:43 ` Jason Gunthorpe
2024-08-23 2:47 ` Baolu Lu
2024-08-26 8:08 ` Tian, Kevin
2024-08-26 8:34 ` Baolu Lu
2024-08-26 8:59 ` Tian, Kevin
2024-08-26 13:51 ` Jason Gunthorpe
2024-08-26 8:47 ` Vasant Hegde
2024-08-26 13:45 ` Jason Gunthorpe
2024-08-22 11:27 ` Yi Liu
2024-08-22 12:44 ` Jason Gunthorpe
2024-08-23 8:58 ` Yi Liu
2024-08-24 14:47 ` Vasant Hegde
2024-08-28 21:52 ` Jacob Pan
2024-08-29 10:51 ` Vasant Hegde
2024-08-29 12:10 ` Jason Gunthorpe
2024-08-29 12:47 ` Vasant Hegde
2024-08-29 13:11 ` Jason Gunthorpe
2024-09-11 10:54 ` Vasant Hegde
2024-08-29 17:40 ` Jacob Pan
[not found] ` <66d0b2a1.630a0220.1dd301.daceSMTPIN_ADDED_BROKEN@mx.google.com>
2024-08-30 15:00 ` Jason Gunthorpe
2024-08-26 8:36 ` Vasant Hegde
2024-08-26 13:56 ` Jason Gunthorpe
2024-08-29 12:34 ` Vasant Hegde [this message]
2024-08-22 1:38 ` Baolu Lu
2024-08-22 12:40 ` Jason Gunthorpe
2024-08-23 2:04 ` Baolu Lu
2024-08-26 6:09 ` Vasant Hegde
2024-08-22 2:10 ` kernel test robot
2024-08-22 3:03 ` kernel test robot
2024-08-22 5:07 ` kernel test robot
2024-08-21 13:35 ` [PATCH 2/5] iommu/amd: Separate page table setup from domain allocation Vasant Hegde
2024-08-21 16:40 ` Jason Gunthorpe
2024-08-21 13:35 ` [PATCH 3/5] iommu/amd: Pass page table type to pdomain_setup_pgtable() Vasant Hegde
2024-08-21 13:35 ` [PATCH 4/5] iommu/amd: Enhance domain_alloc_user() to allocate PASID capable domain Vasant Hegde
2024-08-21 13:35 ` [PATCH 5/5] iommu/amd: Add iommu_ops->domain_alloc_paging support Vasant Hegde
2024-08-21 15:57 ` Jason Gunthorpe
2024-09-11 10:44 ` 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=6adbba52-3f61-42e4-8b1c-d90abf3b192d@amd.com \
--to=vasant.hegde@amd.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@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