public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Yi Liu <yi.l.liu@intel.com>
To: Vasant Hegde <vasant.hegde@amd.com>, <joro@8bytes.org>,
	<jgg@nvidia.com>, <kevin.tian@intel.com>,
	<baolu.lu@linux.intel.com>, <will@kernel.org>
Cc: <alex.williamson@redhat.com>, <eric.auger@redhat.com>,
	<nicolinc@nvidia.com>, <kvm@vger.kernel.org>,
	<chao.p.peng@linux.intel.com>, <iommu@lists.linux.dev>,
	<zhenzhong.duan@intel.com>
Subject: Re: [PATCH v2 0/3] Support attaching PASID to the blocked_domain
Date: Tue, 22 Oct 2024 18:14:18 +0800	[thread overview]
Message-ID: <3c381896-fa24-4445-aefc-6320965d9b0b@intel.com> (raw)
In-Reply-To: <b6f7f648-c509-4e95-a697-f2c09b1cbf6e@amd.com>

On 2024/10/22 17:44, Vasant Hegde wrote:
> Hi Yi,
> 
> 
> On 10/18/2024 11:28 AM, Yi Liu wrote:
>> During the review of iommufd pasid series, Kevin and Jason suggested
>> attaching PASID to the blocked domain hence replacing the usage of
>> remove_dev_pasid() op [1]. This makes sense as it makes the PASID path
>> aligned with the RID path which attaches the RID to the blocked_domain
>> when it is to be blocked. To do it, it requires passing the old domain
>> to the iommu driver. This has been done in [2].
> 
> I understand attaching RID to blocked_domain. But I am not getting why
> we have to do same for PASID. In remove_dev_pasid() path we clear the entry in
> PASID table (AMD case GCR3 table). So no further access is allowed anyway.
> 
> Is it just to align with RID flow -OR- do we have any other reason?

yes, this is also my understanding.:)

Regards,
Yi Liu

> 
> -Vasant
> 
> 
>>
>> This series makes the Intel iommu driver and ARM SMMUv3 driver support
>> attaching PASID to the blocked domain. While the AMD iommu driver does
>> not have the blocked domain yet, so still uses the remove_dev_pasid() op.
>>
>> [1] https://lore.kernel.org/linux-iommu/20240816130202.GB2032816@nvidia.com/
>> [2] https://lore.kernel.org/linux-iommu/20241018055402.23277-2-yi.l.liu@intel.com/
>>
>> v2:
>>   - Add Kevin's r-b
>>   - Adjust the order of patch 03 of v1, it should be the first patch (Baolu)
>>
>> v1: https://lore.kernel.org/linux-iommu/20240912130653.11028-1-yi.l.liu@intel.com/
>>
>> Regards,
>> 	Yi Liu
>>
>> Jason Gunthorpe (1):
>>    iommu/arm-smmu-v3: Make the blocked domain support PASID
>>
>> Yi Liu (2):
>>    iommu: Add a wrapper for remove_dev_pasid
>>    iommu/vt-d: Make the blocked domain support PASID
>>
>>   drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 12 ++++-----
>>   drivers/iommu/intel/iommu.c                 | 19 ++++++++-----
>>   drivers/iommu/intel/pasid.c                 |  3 ++-
>>   drivers/iommu/iommu.c                       | 30 ++++++++++++++++-----
>>   4 files changed, 45 insertions(+), 19 deletions(-)
>>

-- 
Regards,
Yi Liu

      reply	other threads:[~2024-10-22 10:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18  5:58 [PATCH v2 0/3] Support attaching PASID to the blocked_domain Yi Liu
2024-10-18  5:58 ` [PATCH v2 1/3] iommu: Add a wrapper for remove_dev_pasid Yi Liu
2024-10-18 14:39   ` Jason Gunthorpe
2024-10-21  9:35     ` Yi Liu
2024-10-21 12:33       ` Jason Gunthorpe
2024-10-22 12:51         ` Yi Liu
2024-10-23 11:10           ` Vasant Hegde
2024-10-29  5:20             ` Yi Liu
2024-10-29 16:38               ` Vasant Hegde
2024-10-18  5:58 ` [PATCH v2 2/3] iommu/arm-smmu-v3: Make the blocked domain support PASID Yi Liu
2024-10-22  6:06   ` Nicolin Chen
2024-10-18  5:58 ` [PATCH v2 3/3] iommu/vt-d: " Yi Liu
2024-10-18 15:54   ` Jason Gunthorpe
2024-10-21  9:36     ` Yi Liu
2024-10-22  9:44 ` [PATCH v2 0/3] Support attaching PASID to the blocked_domain Vasant Hegde
2024-10-22 10:14   ` Yi Liu [this message]

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=3c381896-fa24-4445-aefc-6320965d9b0b@intel.com \
    --to=yi.l.liu@intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=eric.auger@redhat.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=vasant.hegde@amd.com \
    --cc=will@kernel.org \
    --cc=zhenzhong.duan@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