From: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
To: joro@8bytes.org
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
christian.koenig@amd.com, kevin.tian@intel.com,
jacob.jun.pan@linux.intel.com, ashok.raj@intel.com,
baolu.lu@linux.intel.com, zhangfei.gao@foxmail.com
Subject: [PATCH v3 0/1] IOMMU SVA device driver interface
Date: Wed, 10 Apr 2019 16:15:15 +0100 [thread overview]
Message-ID: <20190410151516.47754-1-jean-philippe.brucker@arm.com> (raw)
This is the device driver API for SVA (Shared Virtual Addressing).
Since v2 I removed the set_sva_ops() IOMMU operation as suggested by
Joerg, instead doing the sva_ops assignment in iommu.c.
The four dev_feature functions are implemented by Lu Baolu's IOMMU-aware
mdev series [2].
iommu_dev_has_feature(dev, IOMMU_DEV_FEAT_SVA) -> true/false
iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) -> 0/err
iommu_dev_disable_feature(dev, IOMMU_DEV_FEAT_SVA) -> 0/err
iommu_dev_feature_enabled(dev, IOMMU_DEV_FEAT_SVA) -> true/false
Patch 1/1 adds the next four functions, once the SVA feature is enabled:
iommu_sva_bind(dev, mm, drvdata) -> handle
iommu_sva_set_ops(handle, iommu_sva_ops) -> 0/err
iommu_sva_get_pasid(handle) -> pasid/invalid
iommu_sva_unbind(handle)
Generic implementation and SMMUv3 support can be found at [3].
[1] https://lore.kernel.org/lkml/20190320150258.3240-1-jean-philippe.brucker@arm.com/
[2] https://lore.kernel.org/lkml/20190325013036.18400-1-baolu.lu@linux.intel.com/
[3] git://linux-arm.org/linux-jpb.git sva/current
http://www.linux-arm.org/git?p=linux-jpb.git;a=shortlog;h=refs/heads/sva/current
Jean-Philippe Brucker (1):
iommu: Bind process address spaces to devices
drivers/iommu/iommu.c | 104 ++++++++++++++++++++++++++++++++++++++++++
include/linux/iommu.h | 70 ++++++++++++++++++++++++++++
2 files changed, 174 insertions(+)
--
2.21.0
next reply other threads:[~2019-04-10 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 15:15 Jean-Philippe Brucker [this message]
2019-04-10 15:15 ` [PATCH v3 1/1] iommu: Bind process address spaces to devices Jean-Philippe Brucker
2019-04-11 15:28 ` Joerg Roedel
2019-04-12 12:23 ` Jean-Philippe Brucker
2019-04-12 14:59 ` Joerg Roedel
2019-04-12 16:05 ` Jean-Philippe Brucker
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=20190410151516.47754-1-jean-philippe.brucker@arm.com \
--to=jean-philippe.brucker@arm.com \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=christian.koenig@amd.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zhangfei.gao@foxmail.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®