All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tina Zhang <tina.zhang@intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Kevin Tian <kevin.tian@intel.com>,
	Lu Baolu <baolu.lu@linux.intel.com>,
	Michael Shavit <mshavit@google.com>, <iommu@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/5] iommu: Support mm PASID 1:n with sva domains
Date: Thu, 10 Aug 2023 10:14:50 +0800	[thread overview]
Message-ID: <7125bb0a-24c0-2d0a-d410-454e86f649b9@intel.com> (raw)
In-Reply-To: <ZNJc8r1eeQZ8GqxY@ziepe.ca>



On 8/8/23 23:19, Jason Gunthorpe wrote:
> On Tue, Aug 08, 2023 at 12:12:42PM -0300, Jason Gunthorpe wrote:
> 
>> Lets please rework this function into two parts
>>
>> The first should be 'iommu_sva_alloc_domain()'
>>
>> It should do the list searching and user management. The usual
>> 'iommu_domain_free()' should be modified to clean it up.
>   
> I suppose we can't quite do this fully since the domain allocation
> needs to use set_dev_pasid to detect compatability :( This is a
> similar problem we had with iommufd too.
> 
> Still, the 'alloc and set_dev_pasid' should be in one function and it
> should be undone with iommu_detach_device_pasid() and
> iommu_domain_free().
> 
> The helper bind/unbind functions should wrapper that sequence.
Make sense. I'll refine the error handling paths in bind/unbind 
functions in the next version.

Thanks,
-Tina
> 
> Jason

  reply	other threads:[~2023-08-10  2:15 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08  7:49 [PATCH 0/5] Share sva domains with all devices bound to a mm Tina Zhang
2023-08-08  7:49 ` [PATCH 1/5] iommu: Add mm_get_pasid() helper function Tina Zhang
2023-08-08 15:02   ` Jason Gunthorpe
2023-08-09  0:31     ` Baolu Lu
2023-08-09  9:47     ` Tian, Kevin
2023-08-09 12:31       ` Jason Gunthorpe
2023-08-08  7:49 ` [PATCH 2/5] iommu: Call helper function to get assigned pasid value Tina Zhang
2023-08-09  0:21   ` Baolu Lu
2023-08-09  9:49     ` Tian, Kevin
2023-08-09 10:58       ` Baolu Lu
2023-08-09 14:48         ` Jason Gunthorpe
2023-08-10  1:37           ` Baolu Lu
2023-08-10 16:30             ` Jason Gunthorpe
2023-08-09 12:35       ` Jason Gunthorpe
2023-08-10  7:52         ` Tian, Kevin
2023-08-10 16:36           ` Jason Gunthorpe
2023-08-11  3:18             ` Tian, Kevin
2023-08-08  7:49 ` [PATCH 3/5] mm: Add structure to keep sva information Tina Zhang
2023-08-08  7:49 ` [PATCH 4/5] iommu: Support mm PASID 1:n with sva domains Tina Zhang
2023-08-08 15:12   ` Jason Gunthorpe
2023-08-08 15:19     ` Jason Gunthorpe
2023-08-10  2:14       ` Tina Zhang [this message]
2023-08-08  7:49 ` [PATCH 5/5] mm: Deprecate pasid field Tina Zhang
2023-08-09  0:18 ` [PATCH 0/5] Share sva domains with all devices bound to a mm Baolu Lu
2023-08-09  9:44   ` Tian, Kevin
2023-08-09 10:51     ` Baolu Lu
2023-08-11  1:06       ` Tina Zhang
2023-08-09 14:46   ` Jason Gunthorpe
2023-08-10  1:23     ` Baolu Lu
2023-08-10  7:44       ` Tian, Kevin
2023-08-09  9:41 ` Tian, Kevin
2023-08-10  1:31   ` Tina Zhang
2023-08-10  7:49     ` Tian, Kevin
2023-08-10 16:27       ` Jason Gunthorpe
2023-08-11  1:12         ` Tina Zhang
2023-08-11  1:07       ` Tina Zhang

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=7125bb0a-24c0-2d0a-d410-454e86f649b9@intel.com \
    --to=tina.zhang@intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mshavit@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.