public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: LKML <linux-kernel@vger.kernel.org>,
	iommu@lists.linux.dev, Jason Gunthorpe <jgg@nvidia.com>,
	"Lu Baolu" <baolu.lu@linux.intel.com>,
	Joerg Roedel <joro@8bytes.org>,
	Jean-Philippe Brucker <jean-philippe@linaro.com>,
	"Robin Murphy" <robin.murphy@arm.com>
Cc: "Will Deacon" <will@kernel.org>, Raj Ashok <ashok.raj@intel.com>,
	"Tian, Kevin" <kevin.tian@intel.com>, Yi Liu <yi.l.liu@intel.com>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	torvalds@linux-foundation.org,
	Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: [PATCH] iommu: Add Kconfig help text for IOMMU_SVA
Date: Sat,  6 May 2023 06:31:34 -0700	[thread overview]
Message-ID: <20230506133134.1492395-1-jacob.jun.pan@linux.intel.com> (raw)

Shared Virtual Addressing (SVA) is not immediately intuitive to people
who work outside IOMMU subsystem, add some explanation to make it less
opaque.
Link: https://lore.kernel.org/lkml/ZE70doFi8X3KgfrV@ziepe.ca/t/#meaa938c91857665b376db59e16b532ba9d4ea013
Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
---
 drivers/iommu/Kconfig | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig
index db98c3f86e8c..0f7181007dc1 100644
--- a/drivers/iommu/Kconfig
+++ b/drivers/iommu/Kconfig
@@ -1,4 +1,4 @@
-# SPDX-License-Identifier: GPL-2.0-only
+# PDX-License-Identifier: GPL-2.0-only
 # The IOVA library may also be used by non-IOMMU_API users
 config IOMMU_IOVA
 	tristate
@@ -155,7 +155,14 @@ config IOMMU_DMA
 
 # Shared Virtual Addressing
 config IOMMU_SVA
-	bool
+	bool "Shared Virtual Addressing"
+	help
+	  IOMMU and CPU share page tables for user processes thus DMA can use
+	  CPU virtual address. Under intel architecture, it is also called
+	  Shared Virtual Memory (SVM).
+	  With SVA, DMA requests are tagged with PCIe Process Address Space ID
+	  (PASID) or Substream ID (ARM SMMU term) with which page tables are
+	  associated.
 
 config FSL_PAMU
 	bool "Freescale IOMMU support"
-- 
2.25.1


             reply	other threads:[~2023-05-06 13:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06 13:31 Jacob Pan [this message]
2023-05-06 15:19 ` [PATCH] iommu: Add Kconfig help text for IOMMU_SVA kernel test robot
2023-05-06 15:39 ` kernel test robot
2023-05-06 15:39 ` kernel test robot
2023-05-06 15:43 ` Linus Torvalds
2023-05-06 22:07   ` Jacob Pan
2023-05-07 18:52     ` Linus Torvalds
2023-05-08 16:40       ` Jacob Pan
2023-05-08 16:42         ` Linus Torvalds
2023-05-08 16:55           ` Jason Gunthorpe
2023-05-08 17:17             ` Linus Torvalds
2023-05-08 20:21               ` Jacob Pan
2023-05-09  0:13                 ` Tian, Kevin
2023-05-09  1:55                 ` Baolu Lu
2023-05-09  0:10               ` Tian, Kevin
2023-05-09 23:06               ` 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=20230506133134.1492395-1-jacob.jun.pan@linux.intel.com \
    --to=jacob.jun.pan@linux.intel.com \
    --cc=ashok.raj@intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jean-philippe@linaro.com \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=torvalds@linux-foundation.org \
    --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