[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ba7a7e6a-8b23-fca0-a8bb-72c4dbfa8390@huawei.com>
Date: Mon, 20 Jan 2020 09:44:51 +0000
From: John Garry <john.garry@...wei.com>
To: Lu Baolu <baolu.lu@...ux.intel.com>,
Joerg Roedel <joro@...tes.org>,
"Greg Kroah-Hartman" <gregkh@...uxfoundation.org>,
Bjorn Helgaas <bhelgaas@...gle.com>
CC: <kevin.tian@...el.com>, <ashok.raj@...el.com>,
<linux-kernel@...r.kernel.org>, <iommu@...ts.linux-foundation.org>,
<jacob.jun.pan@...el.com>, Robin Murphy <robin.murphy@....com>,
"Christoph Hellwig" <hch@....de>
Subject: Re: [RFC PATCH 0/4] iommu: Per-group default domain type
On 01/01/2020 05:26, Lu Baolu wrote:
> An IOMMU group represents the smallest set of devices that are considered
> to be isolated. All devices belonging to an IOMMU group share a default
> domain for DMA APIs. There are two types of default domain: IOMMU_DOMAIN_DMA
> and IOMMU_DOMAIN_IDENTITY. The former means IOMMU translation, while the
> latter means IOMMU by-pass.
>
> Currently, the default domain type for the IOMMU groups is determined
> globally. All IOMMU groups use a single default domain type. The global
> default domain type can be adjusted by kernel build configuration or
> kernel parameters.
>
> More and more users are looking forward to a fine grained default domain
> type. For example, with the global default domain type set to translation,
> the OEM verndors or end users might want some trusted and fast-speed devices
> to bypass IOMMU for performance gains. On the other hand, with global
> default domain type set to by-pass, some devices with limited system
> memory addressing capability might want IOMMU translation to remove the
> bounce buffer overhead.
Hi Lu Baolu,
Do you think that it would be a more common usecase to want
kernel-managed devices to be passthrough for performance reasons and
some select devices to be in DMA domain, like those with limited address
cap or whose drivers request huge amounts of memory?
I just think it would be more manageable to set kernel commandline
parameters for this, i.e. those select few which want DMA domain.
Thanks,
John
>
> This series proposes per-group default domain type to meet these demands.
> It adds a per-device iommu_passthrough attribute. By setting this
> attribute, end users or device vendors are able to tell the IOMMU subsystem
> that this device is willing to use a default domain of IOMMU_DOMAIN_IDENTITY.
> The IOMMU device probe procedure is reformed to pre-allocate groups for
> all devices on a specific bus before adding the devices into the groups.
> This enables the IOMMU device probe precedure to determine a per-group
> default domain type before allocating IOMMU domains and attaching them
> to devices.
>
> Please help to review it. Your comments and suggestions are appricated.
>
> Best regards,
> baolu
>
> Lu Baolu (4):
> driver core: Add iommu_passthrough to struct device
> PCI: Add "pci=iommu_passthrough=" parameter for iommu passthrough
> iommu: Preallocate iommu group when probing devices
> iommu: Determine default domain type before allocating domain
>
> .../admin-guide/kernel-parameters.txt | 5 +
> drivers/iommu/iommu.c | 127 ++++++++++++++----
> drivers/pci/pci.c | 34 +++++
> drivers/pci/pci.h | 1 +
> drivers/pci/probe.c | 2 +
> include/linux/device.h | 3 +
> 6 files changed, 143 insertions(+), 29 deletions(-)
>
Powered by blists - more mailing lists