From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: iommu@lists.linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>,
Joerg Roedel <joro@8bytes.org>,
David Woodhouse <dwmw2@infradead.org>,
Alex Williamson <alex.williamson@redhat.com>,
Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
Raj Ashok <ashok.raj@intel.com>,
Jonathan Cameron <jic23@kernel.org>
Subject: [PATCH 0/4] User API for nested shared virtual address (SVA)
Date: Wed, 18 Sep 2019 16:26:30 -0700 [thread overview]
Message-ID: <1568849194-47874-1-git-send-email-jacob.jun.pan@linux.intel.com> (raw)
This set consists of IOMMU APIs to support SVA in the guest, a.k.a nested
SVA. As the complete SVA support is complex, we break down the enabling
effort into three stages:
1. PCI device direct assignment
2. Fault handling, especially page request service support
3. Mediated device assignment
Each stage includes common API and vendor specific IOMMU driver changes. This
series is the common uAPI for stage #1. It is intended to build consensus on
the interface which all vendors reply on.
This series is extracted from the complete stage1 set which includes VT-d code.
https://lkml.org/lkml/2019/8/15/951
Changes:
- Use spinlock instead of mutex to protect ioasid custom allocators. This is
to support callers in atomic context
- Added more padding to guest PASID bind data for future extensions, suggested
by Joerg.
After much thinking, I did not do name change from PASID to IOASID in the uAPI,
considering we have been using PASID in the rest of uAPIs. IOASID will remain
used within the kernel.
For more discussions lead to this series, checkout LPC 2019 VFIO/IOMMU/PCI
microconference materials.
https://linuxplumbersconf.org/event/4/sessions/66/#20190909
Jacob Pan (2):
iommu/ioasid: Add custom allocators
iommu: Introduce guest PASID bind function
Jean-Philippe Brucker (1):
iommu: Add I/O ASID allocator
Yi L Liu (1):
iommu: Introduce cache_invalidate API
drivers/iommu/Kconfig | 4 +
drivers/iommu/Makefile | 1 +
drivers/iommu/ioasid.c | 432 +++++++++++++++++++++++++++++++++++++++++++++
drivers/iommu/iommu.c | 30 ++++
include/linux/ioasid.h | 75 ++++++++
include/linux/iommu.h | 36 ++++
include/uapi/linux/iommu.h | 169 ++++++++++++++++++
7 files changed, 747 insertions(+)
create mode 100644 drivers/iommu/ioasid.c
create mode 100644 include/linux/ioasid.h
--
2.7.4
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2019-09-18 23:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 23:26 Jacob Pan [this message]
2019-09-18 23:26 ` [PATCH 1/4] iommu: Introduce cache_invalidate API Jacob Pan
2019-09-20 16:32 ` Jean-Philippe Brucker
2019-09-18 23:26 ` [PATCH 2/4] iommu: Add I/O ASID allocator Jacob Pan
2019-09-19 6:30 ` kbuild test robot
2019-09-20 16:33 ` Jean-Philippe Brucker
2019-09-18 23:26 ` [PATCH 3/4] iommu/ioasid: Add custom allocators Jacob Pan
2019-09-20 16:35 ` Jean-Philippe Brucker
2019-09-21 17:42 ` Jacob Pan
2019-09-18 23:26 ` [PATCH 4/4] iommu: Introduce guest PASID bind function Jacob Pan
2019-09-20 16:38 ` 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=1568849194-47874-1-git-send-email-jacob.jun.pan@linux.intel.com \
--to=jacob.jun.pan@linux.intel.com \
--cc=alex.williamson@redhat.com \
--cc=ashok.raj@intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe.brucker@arm.com \
--cc=jic23@kernel.org \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.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