From: Christoph Hellwig Subject: road blocks for using dma-iommu on more than arm64 Date: Sun, 1 Oct 2017 02:02:45 -0700 Message-ID: <20171001090245.GA22124@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org List-Id: iommu@lists.linux-foundation.org Hi all, are there any road blocks for using drivers/iommu/dma-iommu.c for more than just arm64, e.g. also for the Intel/AMD iommus? I've been trying to consolidate the giant amounts of duplicate code in the dma ops implementations for a while, and iommus that provide an iommu_api driver seems like an easy enough target. I remember we had discussions about such things a while ago, so I wonder if its just that no one got to this yet or if there are any known issues that need to be solved first.