From: Jason Wang <jasowang@redhat.com>
To: Liu Yi L <yi.l.liu@intel.com>,
qemu-devel@nongnu.org, mst@redhat.com, pbonzini@redhat.com,
alex.williamson@redhat.com, peterx@redhat.com
Cc: tianyu.lan@intel.com, kevin.tian@intel.com,
jacob.jun.pan@linux.intel.com, kvm@vger.kernel.org,
jun.j.tian@intel.com, eric.auger@redhat.com, yi.y.sun@intel.com,
david@gibson.dropbear.id.au
Subject: Re: [RFC v2 00/22] intel_iommu: expose Shared Virtual Addressing to VM
Date: Fri, 25 Oct 2019 17:49:19 +0800 [thread overview]
Message-ID: <367adad0-eb05-c950-21d7-755fffacbed6@redhat.com> (raw)
In-Reply-To: <1571920483-3382-1-git-send-email-yi.l.liu@intel.com>
On 2019/10/24 下午8:34, Liu Yi L wrote:
> Shared virtual address (SVA), a.k.a, Shared virtual memory (SVM) on Intel
> platforms allow address space sharing between device DMA and applications.
Interesting, so the below figure demonstrates the case of VM. I wonder
how much differences if we compare it with doing SVM between device and
an ordinary process (e.g dpdk)?
Thanks
> SVA can reduce programming complexity and enhance security.
> This series is intended to expose SVA capability to VMs. i.e. shared guest
> application address space with passthru devices. The whole SVA virtualization
> requires QEMU/VFIO/IOMMU changes. This series includes the QEMU changes, for
> VFIO and IOMMU changes, they are in separate series (listed in the "Related
> series").
>
> The high-level architecture for SVA virtualization is as below:
>
> .-------------. .---------------------------.
> | vIOMMU | | Guest process CR3, FL only|
> | | '---------------------------'
> .----------------/
> | PASID Entry |--- PASID cache flush -
> '-------------' |
> | | V
> | | CR3 in GPA
> '-------------'
> Guest
> ------| Shadow |--------------------------|--------
> v v v
> Host
> .-------------. .----------------------.
> | pIOMMU | | Bind FL for GVA-GPA |
> | | '----------------------'
> .----------------/ |
> | PASID Entry | V (Nested xlate)
> '----------------\.------------------------------.
> | | |SL for GPA-HPA, default domain|
> | | '------------------------------'
> '-------------'
> Where:
> - FL = First level/stage one page tables
> - SL = Second level/stage two page tables
>
> The complete vSVA upstream patches are divided into three phases:
> 1. Common APIs and PCI device direct assignment
> 2. Page Request Services (PRS) support
> 3. Mediated device assignment
>
> This RFC patchset is aiming for the phase 1. Works together with the VT-d
> driver[1] changes and VFIO changes[2].
>
> Related series:
> [1] [PATCH v6 00/10] Nested Shared Virtual Address (SVA) VT-d support:
> https://lkml.org/lkml/2019/10/22/953
> <This series is based on this kernel series from Jacob Pan>
>
> [2] [RFC v2 0/3] vfio: support Shared Virtual Addressing from Yi Liu
>
> There are roughly four parts:
> 1. Introduce IOMMUContext as abstract layer between vIOMMU emulator and
> VFIO to avoid direct calling between the two
> 2. Passdown PASID allocation and free to host
> 3. Passdown guest PASID binding to host
> 4. Passdown guest IOMMU cache invalidation to host
>
> The full set can be found in below link:
> https://github.com/luxis1999/qemu.git: sva_vtd_v6_qemu_rfc_v2
>
> Changelog:
> - RFC v1 -> v2:
> Introduce IOMMUContext to abstract the connection between VFIO
> and vIOMMU emulator, which is a replacement of the PCIPASIDOps
> in RFC v1. Modify x-scalable-mode to be string option instead of
> adding a new option as RFC v1 did. Refined the pasid cache management
> and addressed the TODOs mentioned in RFC v1.
> RFC v1: https://patchwork.kernel.org/cover/11033657/
>
> Eric Auger (1):
> update-linux-headers: Import iommu.h
>
> Liu Yi L (20):
> header update VFIO/IOMMU vSVA APIs against 5.4.0-rc3+
> intel_iommu: modify x-scalable-mode to be string option
> vfio/common: add iommu_ctx_notifier in container
> hw/pci: modify pci_setup_iommu() to set PCIIOMMUOps
> hw/pci: introduce pci_device_iommu_context()
> intel_iommu: provide get_iommu_context() callback
> vfio/pci: add iommu_context notifier for pasid alloc/free
> intel_iommu: add virtual command capability support
> intel_iommu: process pasid cache invalidation
> intel_iommu: add present bit check for pasid table entries
> intel_iommu: add PASID cache management infrastructure
> vfio/pci: add iommu_context notifier for pasid bind/unbind
> intel_iommu: bind/unbind guest page table to host
> intel_iommu: replay guest pasid bindings to host
> intel_iommu: replay pasid binds after context cache invalidation
> intel_iommu: do not passdown pasid bind for PASID #0
> vfio/pci: add iommu_context notifier for PASID-based iotlb flush
> intel_iommu: process PASID-based iotlb invalidation
> intel_iommu: propagate PASID-based iotlb invalidation to host
> intel_iommu: process PASID-based Device-TLB invalidation
>
> Peter Xu (1):
> hw/iommu: introduce IOMMUContext
>
> hw/Makefile.objs | 1 +
> hw/alpha/typhoon.c | 6 +-
> hw/arm/smmu-common.c | 6 +-
> hw/hppa/dino.c | 6 +-
> hw/i386/amd_iommu.c | 6 +-
> hw/i386/intel_iommu.c | 1249 +++++++++++++++++++++++++++++++++++++--
> hw/i386/intel_iommu_internal.h | 109 ++++
> hw/i386/trace-events | 6 +
> hw/iommu/Makefile.objs | 1 +
> hw/iommu/iommu.c | 66 +++
> hw/pci-host/designware.c | 6 +-
> hw/pci-host/ppce500.c | 6 +-
> hw/pci-host/prep.c | 6 +-
> hw/pci-host/sabre.c | 6 +-
> hw/pci/pci.c | 27 +-
> hw/ppc/ppc440_pcix.c | 6 +-
> hw/ppc/spapr_pci.c | 6 +-
> hw/s390x/s390-pci-bus.c | 8 +-
> hw/vfio/common.c | 10 +
> hw/vfio/pci.c | 149 +++++
> include/hw/i386/intel_iommu.h | 58 +-
> include/hw/iommu/iommu.h | 113 ++++
> include/hw/pci/pci.h | 13 +-
> include/hw/pci/pci_bus.h | 2 +-
> include/hw/vfio/vfio-common.h | 9 +
> linux-headers/linux/iommu.h | 324 ++++++++++
> linux-headers/linux/vfio.h | 83 +++
> scripts/update-linux-headers.sh | 2 +-
> 28 files changed, 2232 insertions(+), 58 deletions(-)
> create mode 100644 hw/iommu/Makefile.objs
> create mode 100644 hw/iommu/iommu.c
> create mode 100644 include/hw/iommu/iommu.h
> create mode 100644 linux-headers/linux/iommu.h
>
next prev parent reply other threads:[~2019-10-25 9:55 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 12:34 [RFC v2 00/22] intel_iommu: expose Shared Virtual Addressing to VM Liu Yi L
2019-10-24 12:34 ` [RFC v2 01/22] update-linux-headers: Import iommu.h Liu Yi L
2019-10-24 12:34 ` [RFC v2 02/22] header update VFIO/IOMMU vSVA APIs against 5.4.0-rc3+ Liu Yi L
2019-10-24 12:34 ` [RFC v2 03/22] intel_iommu: modify x-scalable-mode to be string option Liu Yi L
2019-11-01 14:57 ` Peter Xu
2019-11-05 9:14 ` Liu, Yi L
2019-11-05 12:50 ` Peter Xu
2019-11-06 9:50 ` Liu, Yi L
2019-10-24 12:34 ` [RFC v2 04/22] hw/iommu: introduce IOMMUContext Liu Yi L
2019-10-27 17:39 ` David Gibson
2019-11-06 11:18 ` Liu, Yi L
2019-10-24 12:34 ` [RFC v2 05/22] vfio/common: add iommu_ctx_notifier in container Liu Yi L
2019-11-01 14:58 ` Peter Xu
2019-11-06 11:08 ` Liu, Yi L
2019-10-24 12:34 ` [RFC v2 06/22] hw/pci: modify pci_setup_iommu() to set PCIIOMMUOps Liu Yi L
2019-10-27 17:43 ` David Gibson
2019-11-06 8:18 ` Liu, Yi L
2019-11-01 18:09 ` Peter Xu
2019-11-06 8:15 ` Liu, Yi L
2019-10-24 12:34 ` [RFC v2 07/22] hw/pci: introduce pci_device_iommu_context() Liu Yi L
2019-10-29 11:50 ` David Gibson
2019-11-06 8:20 ` Liu, Yi L
2019-11-01 18:09 ` Peter Xu
2019-11-06 8:14 ` Liu, Yi L
2019-10-24 12:34 ` [RFC v2 08/22] intel_iommu: provide get_iommu_context() callback Liu Yi L
2019-11-01 14:55 ` Peter Xu
2019-11-06 11:07 ` Liu, Yi L
2019-10-24 12:34 ` [RFC v2 09/22] vfio/pci: add iommu_context notifier for pasid alloc/free Liu Yi L
2019-10-29 12:15 ` David Gibson
2019-11-01 17:26 ` Peter Xu
2019-11-06 12:46 ` Liu, Yi L
2019-11-06 12:14 ` Liu, Yi L
2019-11-20 4:27 ` David Gibson
2019-11-26 7:07 ` Liu, Yi L
2019-10-24 12:34 ` [RFC v2 10/22] intel_iommu: add virtual command capability support Liu Yi L
2019-11-01 18:05 ` Peter Xu
2019-11-06 12:40 ` Liu, Yi L
2019-11-06 14:00 ` Peter Xu
2019-11-12 6:27 ` Liu, Yi L
2019-10-24 12:34 ` [RFC v2 11/22] intel_iommu: process pasid cache invalidation Liu Yi L
2019-11-02 16:05 ` Peter Xu
2019-11-06 5:55 ` Liu, Yi L
2019-10-24 12:34 ` [RFC v2 12/22] intel_iommu: add present bit check for pasid table entries Liu Yi L
2019-11-02 16:20 ` Peter Xu
2019-11-06 8:14 ` Liu, Yi L
2019-10-24 12:34 ` [RFC v2 13/22] intel_iommu: add PASID cache management infrastructure Liu Yi L
2019-11-04 17:08 ` Peter Xu
2019-11-04 20:06 ` Peter Xu
2019-11-06 7:56 ` Liu, Yi L
2019-11-07 15:46 ` Peter Xu
2019-10-24 12:34 ` [RFC v2 14/22] vfio/pci: add iommu_context notifier for pasid bind/unbind Liu Yi L
2019-11-04 16:02 ` David Gibson
2019-11-06 12:22 ` Liu, Yi L
2019-11-06 14:25 ` Peter Xu
2019-10-24 12:34 ` [RFC v2 15/22] intel_iommu: bind/unbind guest page table to host Liu Yi L
2019-11-04 20:25 ` Peter Xu
2019-11-06 8:10 ` Liu, Yi L
2019-11-06 14:27 ` Peter Xu
2019-10-24 12:34 ` [RFC v2 16/22] intel_iommu: replay guest pasid bindings " Liu Yi L
2019-10-24 12:34 ` [RFC v2 17/22] intel_iommu: replay pasid binds after context cache invalidation Liu Yi L
2019-10-24 12:34 ` [RFC v2 18/22] intel_iommu: do not passdown pasid bind for PASID #0 Liu Yi L
2019-10-24 12:34 ` [RFC v2 19/22] vfio/pci: add iommu_context notifier for PASID-based iotlb flush Liu Yi L
2019-10-24 12:34 ` [RFC v2 20/22] intel_iommu: process PASID-based iotlb invalidation Liu Yi L
2019-10-24 12:34 ` [RFC v2 21/22] intel_iommu: propagate PASID-based iotlb invalidation to host Liu Yi L
2019-10-24 12:34 ` [RFC v2 22/22] intel_iommu: process PASID-based Device-TLB invalidation Liu Yi L
2019-10-25 6:21 ` [RFC v2 00/22] intel_iommu: expose Shared Virtual Addressing to VM no-reply
2019-10-25 6:30 ` no-reply
2019-10-25 9:49 ` Jason Wang [this message]
2019-10-25 10:12 ` Tian, Kevin
2019-10-31 4:33 ` Jason Wang
2019-10-31 5:39 ` Tian, Kevin
2019-10-31 14:07 ` Liu, Yi L
2019-11-01 7:29 ` Jason Wang
2019-11-01 7:46 ` Tian, Kevin
2019-11-01 8:04 ` Jason Wang
2019-11-01 8:09 ` Jason Wang
2019-11-02 7:35 ` Tian, Kevin
2019-11-04 17:22 ` Peter Xu
2019-11-05 9:09 ` Liu, Yi L
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=367adad0-eb05-c950-21d7-755fffacbed6@redhat.com \
--to=jasowang@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=eric.auger@redhat.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jun.j.tian@intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tianyu.lan@intel.com \
--cc=yi.l.liu@intel.com \
--cc=yi.y.sun@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;
as well as URLs for NNTP newsgroup(s).