[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190529061626.GA26055@infradead.org>
Date: Tue, 28 May 2019 23:16:26 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Lu Baolu <baolu.lu@...ux.intel.com>
Cc: David Woodhouse <dwmw2@...radead.org>,
Joerg Roedel <joro@...tes.org>, kevin.tian@...el.com,
ashok.raj@...el.com, dima@...sta.com, tmurphy@...sta.com,
linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org,
jacob.jun.pan@...el.com
Subject: Re: [PATCH v4 10/15] iommu/vt-d: Probe DMA-capable ACPI name space
devices
On Sat, May 25, 2019 at 01:41:31PM +0800, Lu Baolu wrote:
> Some platforms may support ACPI name-space enumerated devices
> that are capable of generating DMA requests. Platforms which
> support DMA remapping explicitly declares any such DMA-capable
> ACPI name-space devices in the platform through ACPI Name-space
> Device Declaration (ANDD) structure and enumerate them through
> the Device Scope of the appropriate remapping hardware unit.
>
> Signed-off-by: Lu Baolu <baolu.lu@...ux.intel.com>
Isn't this something that should be handled through the IOMMU API so
that it covers other IOMMU types as well?
How does this scheme compare to the one implemented in
drivers/acpi/arm64/iort.c?
Powered by blists - more mailing lists