Linux IOMMU Development
 help / color / mirror / Atom feed
From: Vasant Hegde <vasant.hegde@amd.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Baolu Lu <baolu.lu@linux.intel.com>,
	iommu@lists.linux.dev, joro@8bytes.org, will@kernel.org,
	robin.murphy@arm.com, suravee.suthikulpanit@amd.com,
	yi.l.liu@intel.com, Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [PATCH RFCv2] iommu: Add domain type and flag to domain_alloc_paging()
Date: Mon, 12 Aug 2024 14:51:56 +0530	[thread overview]
Message-ID: <fe275b31-41ad-4d7f-89bd-bef4788f58bf@amd.com> (raw)
In-Reply-To: <20240809134454.GF1985367@ziepe.ca>

Jason,


On 8/9/2024 7:14 PM, Jason Gunthorpe wrote:
> On Fri, Aug 09, 2024 at 12:13:47PM +0530, Vasant Hegde wrote:
>> Jason,
>>
>>
>> On 8/8/2024 6:38 PM, Jason Gunthorpe wrote:
>>> On Wed, Aug 07, 2024 at 10:16:29PM -0300, Jason Gunthorpe wrote:
>>>> On Wed, Aug 07, 2024 at 03:29:47PM -0300, Jason Gunthorpe wrote:
>>>>>> @Baolu, Do we need to make any changes to intel driver?
>>>>>
>>>>> I think Intel ignores this issue, they have nice HW and their RID can
>>>>> use both of their supported domain formats in all cases.
>>>>
>>>> On second thought it does need to accept, but ignore the new flags..
>>>
>>> And probably HW that does not support PASID should reject the
>>> IOMMU_HWPT_ALLOC_PASID flag at least.
>>
>>
>> You mean error out if IOMMU or device doesnot support PASID?
> 
> Just the iommu, yes.
> 
> Like in AMD terms if there is no AMDv2 page table support then fail
> it.
> 
>>> Maybe IOMMU_HWPT_ALLOC_DEV_PASID can be reasonably ignored if the HW
>>> doesn't support PASID.
>>  
>> You mean make it as optional flag? Meaning if HW doesn't support PASID then
>> still allocate a domain without PASID capability?
> 
> Yes, for the RID domain it seems harmless to ignore, I'm not really
> sure on this though.
> 
> Otherwise we'd want to report pasid support through a INFO return so
> userspace knows if it should specify this flag.

Let me summarize and see if I got everything right.

- Enhance iommufd_get_hw_info ioctl to get device PASID capability
  HW driver will implement iommu_ops->capable() to check PASID capability

- Userspace will use above info and calls iommu_ops->domain_alloc_user() with
  appropriate flag (If PASID capability present then pass
  IOMMU_HWPT_ALLOC_DEV_PASID as flag).

- HW driver : If IOMMU and dev supports PASID then allocate PASID capable
  domain, else allocate normal domain.

- When attaching PASID to device (RID), PASID attachment will pass only domain
supports PASID, else it will fail.

- IOMMU_HWPT_ALLOC_PASID  flag is optional:
  If we endup implementing this flag, then it will allocate PASID capable domain
if HW IOMMU supports it (It will not check device capability).


Does this flow makes sense?

-Vasant

  reply	other threads:[~2024-08-12  9:22 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-01 14:45 [PATCH RFCv2] iommu: Add domain type and flag to domain_alloc_paging() Vasant Hegde
2024-08-02  0:44 ` Baolu Lu
2024-08-02  5:53   ` Vasant Hegde
2024-08-06 12:34     ` Jason Gunthorpe
2024-08-06 14:41       ` Vasant Hegde
2024-08-06 17:32         ` Jason Gunthorpe
2024-08-07  5:49           ` Baolu Lu
2024-08-07  9:32             ` Vasant Hegde
2024-08-07 12:33             ` Jason Gunthorpe
2024-08-07  9:30           ` Vasant Hegde
2024-08-07 13:59             ` Jason Gunthorpe
2024-08-07 16:52               ` Vasant Hegde
2024-08-07 18:29                 ` Jason Gunthorpe
2024-08-08  1:16                   ` Jason Gunthorpe
2024-08-08 13:08                     ` Jason Gunthorpe
2024-08-09  6:43                       ` Vasant Hegde
2024-08-09 13:44                         ` Jason Gunthorpe
2024-08-12  9:21                           ` Vasant Hegde [this message]
2024-08-13 16:22                             ` Jason Gunthorpe
2024-08-14 10:54                               ` Vasant Hegde
2024-08-09  5:36                   ` Vasant Hegde
2024-08-12 12:07                   ` Yi Liu
2024-08-13  9:40                   ` Tian, Kevin
2024-08-13 16:20                     ` Jason Gunthorpe
2024-08-14  2:38                       ` Tian, Kevin
2024-08-14 22:40                         ` Jason Gunthorpe
2024-08-15  3:28                           ` Vasant Hegde
2024-08-15  4:58                             ` Yi Liu
2024-08-15 13:06                               ` Jason Gunthorpe
2024-08-16 11:59                                 ` Yi Liu
2024-08-15  4:59                             ` Baolu Lu
2024-08-15 13:47                               ` Jason Gunthorpe
2024-08-16  8:17                                 ` Vasant Hegde
2024-08-16 12:01                                   ` Yi Liu
2024-08-16 18:37                                   ` Jason Gunthorpe
2024-08-19  8:27                                     ` Vasant Hegde
2024-08-19 17:52                                       ` Jason Gunthorpe
2024-08-20  8:18                                         ` Vasant Hegde
2024-08-15 13:05                             ` Jason Gunthorpe
2024-08-12 12:01               ` Yi Liu

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=fe275b31-41ad-4d7f-89bd-bef4788f58bf@amd.com \
    --to=vasant.hegde@amd.com \
    --cc=alex.williamson@redhat.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=joro@8bytes.org \
    --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