| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20191202121927.2fef85ba@jacob-builder>
Date: Mon, 2 Dec 2019 12:19:27 -0800
From: Jacob Pan <jacob.jun.pan@...ux.intel.com>
To: Lu Baolu <baolu.lu@...ux.intel.com>
Cc: Joerg Roedel <joro@...tes.org>,
David Woodhouse <dwmw2@...radead.org>,
Alex Williamson <alex.williamson@...hat.com>,
ashok.raj@...el.com, sanjay.k.kumar@...el.com,
kevin.tian@...el.com, yi.l.liu@...el.com, yi.y.sun@...el.com,
Peter Xu <peterx@...hat.com>, iommu@...ts.linux-foundation.org,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
jacob.jun.pan@...ux.intel.com
Subject: Re: [PATCH v2 0/8] Use 1st-level for DMA remapping
On Thu, 28 Nov 2019 10:25:42 +0800
Lu Baolu <baolu.lu@...ux.intel.com> wrote:
> Intel VT-d in scalable mode supports two types of page talbes
tables
> for DMA translation: the first level page table and the second
> level page table. The first level page table uses the same
> format as the CPU page table, while the second level page table
> keeps compatible with previous formats. The software is able
> to choose any one of them for DMA remapping according to the use
> case.
>
> This patchset aims to move IOVA (I/O Virtual Address) translation
move guest IOVA only, right?
> to 1st-level page table in scalable mode. This will simplify vIOMMU
> (IOMMU simulated by VM hypervisor) design by using the two-stage
> translation, a.k.a. nested mode translation.
>
> As Intel VT-d architecture offers caching mode, guest IOVA (GIOVA)
> support is now implemented in a shadow page manner. The device
> simulation software, like QEMU, has to figure out GIOVA->GPA mappings
> and write them to a shadowed page table, which will be used by the
> physical IOMMU. Each time when mappings are created or destroyed in
> vIOMMU, the simulation software has to intervene. Hence, the changes
> on GIOVA->GPA could be shadowed to host.
>
>
> .-----------.
> | vIOMMU |
> |-----------| .--------------------.
> | |IOTLB flush trap | QEMU |
> .-----------. (map/unmap) |--------------------|
> |GIOVA->GPA |---------------->| .------------. |
> '-----------' | | GIOVA->HPA | |
> | | | '------------' |
> '-----------' | |
> | |
> '--------------------'
> |
> <------------------------------------
> |
> v VFIO/IOMMU API
> .-----------.
> | pIOMMU |
> |-----------|
> | |
> .-----------.
> |GIOVA->HPA |
> '-----------'
> | |
> '-----------'
>
> In VT-d 3.0, scalable mode is introduced, which offers two-level
> translation page tables and nested translation mode. Regards to
> GIOVA support, it can be simplified by 1) moving the GIOVA support
> over 1st-level page table to store GIOVA->GPA mapping in vIOMMU,
> 2) binding vIOMMU 1st level page table to the pIOMMU, 3) using pIOMMU
> second level for GPA->HPA translation, and 4) enable nested (a.k.a.
> dual-stage) translation in host. Compared with current shadow GIOVA
> support, the new approach makes the vIOMMU design simpler and more
> efficient as we only need to flush the pIOMMU IOTLB and possible
> device-IOTLB when an IOVA mapping in vIOMMU is torn down.
>
> .-----------.
> | vIOMMU |
> |-----------| .-----------.
> | |IOTLB flush trap | QEMU |
> .-----------. (unmap) |-----------|
> |GIOVA->GPA |---------------->| |
> '-----------' '-----------'
> | | |
> '-----------' |
> <------------------------------
> | VFIO/IOMMU
> | cache invalidation and
> | guest gpd bind interfaces
> v
> .-----------.
> | pIOMMU |
> |-----------|
> .-----------.
> |GIOVA->GPA |<---First level
> '-----------'
> | GPA->HPA |<---Scond level
> '-----------'
> '-----------'
>
> This patch set includes two parts. The former part implements the
> per-domain page table abstraction, which makes the page table
> difference transparent to various map/unmap APIs. The later part
s/later/latter/
> applies the first level page table for IOVA translation unless the
> DOMAIN_ATTR_NESTING domain attribution has been set, which indicates
> nested mode in use.
>
Maybe I am reading this wrong, but shouldn't it be the opposite?
i.e. Use FL page table for IOVA if it is a nesting domain?
> Based-on-idea-by: Ashok Raj <ashok.raj@...el.com>
> Based-on-idea-by: Kevin Tian <kevin.tian@...el.com>
> Based-on-idea-by: Liu Yi L <yi.l.liu@...el.com>
> Based-on-idea-by: Jacob Pan <jacob.jun.pan@...ux.intel.com>
> Based-on-idea-by: Sanjay Kumar <sanjay.k.kumar@...el.com>
> Based-on-idea-by: Lu Baolu <baolu.lu@...ux.intel.com>
>
> Change log:
>
> v1->v2
> - The first series was posted here
> https://lkml.org/lkml/2019/9/23/297
> - Use per domain page table ops to handle different page tables.
> - Use first level for DMA remapping by default on both bare metal
> and vm guest.
> - Code refine according to code review comments for v1.
>
> Lu Baolu (8):
> iommu/vt-d: Add per domain page table ops
> iommu/vt-d: Move domain_flush_cache helper into header
> iommu/vt-d: Implement second level page table ops
> iommu/vt-d: Apply per domain second level page table ops
> iommu/vt-d: Add first level page table interfaces
> iommu/vt-d: Implement first level page table ops
> iommu/vt-d: Identify domains using first level page table
> iommu/vt-d: Add set domain DOMAIN_ATTR_NESTING attr
>
> drivers/iommu/Makefile | 2 +-
> drivers/iommu/intel-iommu.c | 412
> +++++++++++++++++++++++------ drivers/iommu/intel-pgtable.c |
> 376 ++++++++++++++++++++++++++ include/linux/intel-iommu.h |
> 64 ++++- include/trace/events/intel_iommu.h | 60 +++++
> 5 files changed, 837 insertions(+), 77 deletions(-)
> create mode 100644 drivers/iommu/intel-pgtable.c
>
[Jacob Pan]
Powered by blists - more mailing lists