From: Tina Zhang <tina.zhang@intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Michael Shavit <mshavit@google.com>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
Tina Zhang <tina.zhang@intel.com>
Subject: [RFC PATCH 0/6] Share sva domain with all devices bound to a mm
Date: Fri, 7 Jul 2023 09:34:35 +0800 [thread overview]
Message-ID: <20230707013441.365583-1-tina.zhang@intel.com> (raw)
During a sva domain's life time, which begins with binding a device to a
mm and ends by releasing all the bound devices from that mm, there is only
one PASID assigned for this sva domain. From platform perspective,
supporting 1:1 mapping between mm PASID and sva domain allows a sva domain
to be shared by mm's all bound devices issuing DMA transactions using the
assigned PASID.
To support mm PASID 1:1 with sva domain, each mm needs to keep both a
reference of an allocated sva domain and its corresponding PASID. However,
currently, mm struct only has one pasid field for sva usage, which is used
to keep the info of an assigned PASID. That pasid field cannot provide
sufficient info to build up the 1:1 mapping between sva domain and PASID.
This patch-set fills the gap by adding an mm_iommu field[1], whose type is
mm_iommu_data struct, to replace the old pasid field. The introduced
mm_iommu_data struct keeps info of both a sva domain reference and an
assigned PASID.
[1]: https://lore.kernel.org/linux-iommu/ZIBxPd1%2FJCAle6yP@nvidia.com/
Tina Zhang (6):
iommu: Add two pasid helper functions
iommu: Call helper functions to get/set assigned pasid value
iommu: Introduce struct iommu_mm_data
mm: Add iommu_mm field to mm_struct
iommu: Support mm PASID 1:1 with sva domain
mm: Deprecate pasid field
arch/x86/kernel/traps.c | 2 +-
.../iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c | 12 ++--
drivers/iommu/intel/svm.c | 8 +--
drivers/iommu/iommu-sva.c | 68 ++++++++++++-------
drivers/iommu/iommu.c | 3 +
include/linux/iommu.h | 25 ++++++-
include/linux/mm_types.h | 2 +
mm/init-mm.c | 2 +-
8 files changed, 84 insertions(+), 38 deletions(-)
--
2.34.1
next reply other threads:[~2023-07-07 1:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 1:34 Tina Zhang [this message]
2023-07-07 1:34 ` [RFC PATCH 1/6] iommu: Add two pasid helper functions Tina Zhang
2023-07-07 1:34 ` [RFC PATCH 2/6] iommu: Call helper functions to get/set assigned pasid value Tina Zhang
2023-07-07 1:34 ` [RFC PATCH 3/6] iommu: Introduce struct iommu_mm_data Tina Zhang
2023-07-07 1:34 ` [RFC PATCH 4/6] mm: Add iommu_mm field to mm_struct Tina Zhang
2023-07-07 1:34 ` [RFC PATCH 5/6] iommu: Support mm PASID 1:1 with sva domain Tina Zhang
2023-07-10 17:28 ` Jason Gunthorpe
2023-07-11 1:42 ` Zhang, Tina
2023-07-11 2:43 ` Baolu Lu
2023-07-11 14:18 ` Jason Gunthorpe
2023-07-17 8:47 ` Yanfei Xu
2023-07-07 1:34 ` [RFC PATCH 6/6] mm: Deprecate pasid field Tina Zhang
2023-07-10 17:29 ` Jason Gunthorpe
2023-07-11 1:46 ` Zhang, Tina
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=20230707013441.365583-1-tina.zhang@intel.com \
--to=tina.zhang@intel.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=linux-kernel@vger.kernel.org \
--cc=mshavit@google.com \
--cc=will@kernel.org \
/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