From: Baolu Lu <baolu.lu@linux.intel.com>
To: "tina.zhang" <tina.zhang@intel.com>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
Nicolin Chen <nicolinc@nvidia.com>
Cc: baolu.lu@linux.intel.com, Yi Liu <yi.l.liu@intel.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
iommu@lists.linux.dev, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iommu: Move pasid array from group to device
Date: Tue, 1 Aug 2023 16:40:16 +0800 [thread overview]
Message-ID: <b67d6f3f-95f0-0421-49ff-471032de0963@linux.intel.com> (raw)
In-Reply-To: <1254d61b-1f4e-2ef3-c3dc-95180f26f08c@intel.com>
On 2023/8/1 16:07, tina.zhang wrote:
> Hi Baolu,
Hi Tina,
> Although this patch moves the domain reference pointer from a per-group
> structure to a per-device structure, the domain life-cycle is still
> expected to be managed per-group (i.e., iommu_domain_free() is called in
> iommu_group_release()). Is this what we expect?
The lifecycle of an iommu domain is independent of the lifecycle of the
iommu group that it is attached to. The system domains, such as the
default domain and the blocking domain, are allocated and managed by the
iommu core. These domains are freed when the group is freed.
However, any device driver can allocate its own iommu domains. The
device driver can set/remove the domain to/from the RID or PASID of the
device.
Best regards,
baolu
next prev parent reply other threads:[~2023-08-01 8:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 6:31 [PATCH 0/2] iommu: Make pasid array per device Lu Baolu
2023-08-01 6:31 ` [PATCH 1/2] iommu: Consolidate pasid dma ownership check Lu Baolu
2023-08-01 7:03 ` Tian, Kevin
2023-08-01 7:43 ` Baolu Lu
2023-08-02 1:39 ` Tian, Kevin
2023-08-02 3:20 ` Baolu Lu
2023-08-01 6:31 ` [PATCH 2/2] iommu: Move pasid array from group to device Lu Baolu
[not found] ` <1254d61b-1f4e-2ef3-c3dc-95180f26f08c@intel.com>
2023-08-01 8:40 ` Baolu Lu [this message]
2023-08-02 14:15 ` [PATCH 0/2] iommu: Make pasid array per device Jason Gunthorpe
2023-08-03 0:44 ` Tian, Kevin
2023-08-03 15:18 ` Jason Gunthorpe
2023-08-04 0:57 ` Tian, Kevin
2023-08-04 2:20 ` Baolu Lu
2023-08-04 2:30 ` Baolu Lu
2023-08-04 13:12 ` Jason Gunthorpe
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=b67d6f3f-95f0-0421-49ff-471032de0963@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jean-philippe@linaro.org \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=tina.zhang@intel.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
all inboxes | Powered by JetHome®