Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp6351680yba; Wed, 1 May 2019 10:31:02 -0700 (PDT) X-Google-Smtp-Source: APXvYqz/XpiZuFuzSfIbdSWuYxilkfzmYXj0KmECVeHs6wM2Dpe64VyrWOFEga+WtQLkgdFY2zT4 X-Received: by 2002:a65:5c82:: with SMTP id a2mr24807913pgt.378.1556731862864; Wed, 01 May 2019 10:31:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556731862; cv=none; d=google.com; s=arc-20160816; b=JEkGEtEzxUiyhWZGCOJYIlonF9raSIpy72Ucs/N+ZlMApvNAvQctP/zrbRagbVO6NL z5HpRUfg5gHsy5uBqZ5bRSDA3ulxCpHios7ORmiiEziQzFqS3KGJ69q+XxVHGRU2LOjz 3Xp3/nw1S4oBvLk2TNudGA3QU4vp3YMsOKHnMWZfMkLoG65GYJkUTa1ygqWAWZXvS80z d4myoZZGF482OiZKjikQcYooaebQ1dhXZuXsKmfOrxvJFBoc+rZ2CSAURhBKVdvF/ega R3asC/Km7+iU6eo9QPnMybW7sw/I1jzm6z28n1QXxxHErXrkvNRGYuITvETDzn0WPl8Y FwNw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=7jxrngcYyPX6LgYwpQghYjSa+r8p9Rt9YbWt9owXq2I=; b=bwybpIYDd4//+tOtcL3bZY39ajNgaHrxJoMCL5J2Jp8lBR3+J7AFPn/cobwAZNR31N 8LdDO+lE6znh2nGpfelMnlYsYITRQSf8FSDGOkw6uDo6oszJjOIfXE1JJLohWN9C5yR+ ZkWbQZX7PDeWE1NoCnDSK9Y8qgm+LOTYQY/8HZ0bqCELJjTDrxZQhBsPXfcGmnp+GpbA 2oeiiBXJxCNzN4J4Ub0gowxbUUNeIRQ8ti4S1pNbLUdjgluy4htGAmm5Bhv16VM5gFvz YLhu78tE5rGO0dGRmDGiH4dzyxgWk7RP8FjnoOI4tQbx8WVhGivZmEkLNerZaAx35ndV JUwg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e15si41749269pfn.31.2019.05.01.10.30.46; Wed, 01 May 2019 10:31:02 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726225AbfEAR3d (ORCPT + 99 others); Wed, 1 May 2019 13:29:33 -0400 Received: from verein.lst.de ([213.95.11.211]:54065 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726019AbfEAR3d (ORCPT ); Wed, 1 May 2019 13:29:33 -0400 Received: by newverein.lst.de (Postfix, from userid 2407) id 09DA468AFE; Wed, 1 May 2019 19:29:12 +0200 (CEST) Date: Wed, 1 May 2019 19:29:12 +0200 From: Christoph Hellwig To: Paul Burton Cc: Christoph Hellwig , Ralf Baechle , James Hogan , Ley Foon Tan , Michal Simek , Bartlomiej Zolnierkiewicz , "linux-mips@vger.kernel.org" , "iommu@lists.linux-foundation.org" , "linux-kernel@vger.kernel.org" , "linux-fbdev@vger.kernel.org" Subject: Re: [PATCH 4/7] dma-direct: provide generic support for uncached kernel segments Message-ID: <20190501172912.GA19375@lst.de> References: <20190430110032.25301-1-hch@lst.de> <20190430110032.25301-5-hch@lst.de> <20190501171857.chfxqntvm6r4xrr4@pburton-laptop> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="ew6BAiZeqk4r7MaW" Content-Disposition: inline In-Reply-To: <20190501171857.chfxqntvm6r4xrr4@pburton-laptop> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --ew6BAiZeqk4r7MaW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, May 01, 2019 at 05:18:59PM +0000, Paul Burton wrote: > I'm not so sure about this part though. > > On MIPS we currently don't clear the allocated memory with memset. Is > doing that really necessary? We are clearling it on mips, it is inside dma_direct_alloc_pages. > If it is necessary then as-is this code will clear the allocated memory > using uncached writes which will be pretty slow. It would be much more > efficient to perform the memset before arch_dma_prep_coherent() & before > converting ret to an uncached address. Yes, we could do that. --ew6BAiZeqk4r7MaW Content-Type: text/x-patch; charset=us-ascii Content-Disposition: attachment; filename="0001-dma-direct-provide-generic-support-for-uncached-kern.patch" From 247ca658ebeb7c8d04918747ec8a0da45c36bcb8 Mon Sep 17 00:00:00 2001 From: Christoph Hellwig Date: Sun, 28 Apr 2019 13:23:26 -0500 Subject: dma-direct: provide generic support for uncached kernel segments A few architectures support uncached kernel segments. In that case we get an uncached mapping for a given physica address by using an offset in the uncached segement. Implement support for this scheme in the generic dma-direct code instead of duplicating it in arch hooks. Signed-off-by: Christoph Hellwig --- arch/Kconfig | 8 ++++++++ include/linux/dma-noncoherent.h | 3 +++ kernel/dma/direct.c | 17 +++++++++++++++-- 3 files changed, 26 insertions(+), 2 deletions(-) diff --git a/arch/Kconfig b/arch/Kconfig index 33687dddd86a..ea22a8c894ec 100644 --- a/arch/Kconfig +++ b/arch/Kconfig @@ -249,6 +249,14 @@ config ARCH_HAS_FORTIFY_SOURCE config ARCH_HAS_SET_MEMORY bool +# +# Select if arch has an uncached kernel segment and provides the +# uncached_kernel_address / cached_kernel_address symbols to use it +# +config ARCH_HAS_UNCACHED_SEGMENT + select ARCH_HAS_DMA_PREP_COHERENT + bool + # Select if arch init_task must go in the __init_task_data section config ARCH_TASK_STRUCT_ON_STACK bool diff --git a/include/linux/dma-noncoherent.h b/include/linux/dma-noncoherent.h index 9741767e400f..7e0126a04e02 100644 --- a/include/linux/dma-noncoherent.h +++ b/include/linux/dma-noncoherent.h @@ -80,4 +80,7 @@ static inline void arch_dma_prep_coherent(struct page *page, size_t size) } #endif /* CONFIG_ARCH_HAS_DMA_PREP_COHERENT */ +void *uncached_kernel_address(void *addr); +void *cached_kernel_address(void *addr); + #endif /* _LINUX_DMA_NONCOHERENT_H */ diff --git a/kernel/dma/direct.c b/kernel/dma/direct.c index 2c2772e9702a..6688e1cee7d1 100644 --- a/kernel/dma/direct.c +++ b/kernel/dma/direct.c @@ -171,6 +171,13 @@ void *dma_direct_alloc_pages(struct device *dev, size_t size, *dma_handle = phys_to_dma(dev, page_to_phys(page)); } memset(ret, 0, size); + + if (IS_ENABLED(CONFIG_ARCH_HAS_UNCACHED_SEGMENT) && + !dev_is_dma_coherent(dev) && !(attrs & DMA_ATTR_NON_CONSISTENT)) { + arch_dma_prep_coherent(page, size); + ret = uncached_kernel_address(ret); + } + return ret; } @@ -189,13 +196,18 @@ void dma_direct_free_pages(struct device *dev, size_t size, void *cpu_addr, if (force_dma_unencrypted()) set_memory_encrypted((unsigned long)cpu_addr, 1 << page_order); + + if (IS_ENABLED(CONFIG_ARCH_HAS_UNCACHED_SEGMENT) && + !dev_is_dma_coherent(dev) && !(attrs & DMA_ATTR_NON_CONSISTENT)) + cpu_addr = cached_kernel_address(cpu_addr); __dma_direct_free_pages(dev, size, virt_to_page(cpu_addr)); } void *dma_direct_alloc(struct device *dev, size_t size, dma_addr_t *dma_handle, gfp_t gfp, unsigned long attrs) { - if (!dev_is_dma_coherent(dev)) + if (!IS_ENABLED(CONFIG_ARCH_HAS_UNCACHED_SEGMENT) && + !dev_is_dma_coherent(dev)) return arch_dma_alloc(dev, size, dma_handle, gfp, attrs); return dma_direct_alloc_pages(dev, size, dma_handle, gfp, attrs); } @@ -203,7 +215,8 @@ void *dma_direct_alloc(struct device *dev, size_t size, void dma_direct_free(struct device *dev, size_t size, void *cpu_addr, dma_addr_t dma_addr, unsigned long attrs) { - if (!dev_is_dma_coherent(dev)) + if (!IS_ENABLED(CONFIG_ARCH_HAS_UNCACHED_SEGMENT) && + !dev_is_dma_coherent(dev)) arch_dma_free(dev, size, cpu_addr, dma_addr, attrs); else dma_direct_free_pages(dev, size, cpu_addr, dma_addr, attrs); -- 2.20.1 --ew6BAiZeqk4r7MaW--