From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E1C93C2BA83 for ; Mon, 17 Feb 2020 08:01:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B5C742064C for ; Mon, 17 Feb 2020 08:01:41 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="laCY6zS4" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727227AbgBQIBk (ORCPT ); Mon, 17 Feb 2020 03:01:40 -0500 Received: from bombadil.infradead.org ([198.137.202.133]:40664 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726267AbgBQIBk (ORCPT ); Mon, 17 Feb 2020 03:01:40 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=1j0IAc2wKeBPF3EDz/FuH2CGkeuAUIMTXnv9GxQihUQ=; b=laCY6zS4mQ2Zr6pPzTz9RMFkPB aq8u9QwyM12JK66Qndh5ysuDQT7YWdhal6HppCLdRfq3RhQqRLZxwf9Avtnn7LNvVj9bTA86gRZZs 2pf0IzYRg3HLSEaeXkZsmqsrMm5Fs88MQKNUi96ntO0mwoONxQiBMwNwW3MoXzOkNNymMAm/dGay4 dq1XRT3QEbhhVjP/XZbC3NpOIsOcXBTmZi5aYofeKm/4Aeax/thgKzJyKt0MS8IsakXXUfnvLsiHv qbf9ZH8eHtvTZnRsnlfzBxI95QKxO7++DDhYiGA4cHVMMAIeOzwUXs94ubm56ew/gL4fgrpDNAF08 szEHi0kQ==; Received: from hch by bombadil.infradead.org with local (Exim 4.92.3 #3 (Red Hat Linux)) id 1j3bLW-0004e0-MJ; Mon, 17 Feb 2020 08:01:38 +0000 Date: Mon, 17 Feb 2020 00:01:38 -0800 From: Christoph Hellwig To: "Isaac J. Manjarres" Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Liam Mark , joro@8bytes.org, pratikp@codeaurora.org, kernel-team@android.com Subject: Re: [RFC PATCH] iommu/dma: Allow drivers to reserve an iova range Message-ID: <20200217080138.GB10342@infradead.org> References: <1581721096-16235-1-git-send-email-isaacm@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1581721096-16235-1-git-send-email-isaacm@codeaurora.org> X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 14, 2020 at 02:58:16PM -0800, Isaac J. Manjarres wrote: > From: Liam Mark > > Some devices have a memory map which contains gaps or holes. > In order for the device to have as much IOVA space as possible, > allow its driver to inform the DMA-IOMMU layer that it should > not allocate addresses from these holes. Layering violation. dma-iommu is the translation layer between the DMA API and the IOMMU API. And calls into it from drivers performing DMA mappings need to go through the DMA API (and be documented there).