From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de ([213.95.11.211]:51697 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726664AbfJaPsG (ORCPT ); Thu, 31 Oct 2019 11:48:06 -0400 Date: Thu, 31 Oct 2019 16:47:59 +0100 From: Christoph Hellwig Subject: Re: [PATCH] dma/direct: turn ARCH_ZONE_DMA_BITS into a variable Message-ID: <20191031154759.GA7162@lst.de> References: <20191031152837.15253-1-nsaenzjulienne@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191031152837.15253-1-nsaenzjulienne@suse.de> Sender: linux-s390-owner@vger.kernel.org List-ID: To: Nicolas Saenz Julienne Cc: Christoph Hellwig , Marek Szyprowski , Robin Murphy , Catalin Marinas , Will Deacon , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , Heiko Carstens , Vasily Gorbik , Christian Borntraeger , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, iommu@lists.linux-foundation.org On Thu, Oct 31, 2019 at 04:28:37PM +0100, Nicolas Saenz Julienne wrote: > Some architectures, notably ARM, are interested in tweaking this > depending on their runtime DMA addressing limitations. > > Signed-off-by: Nicolas Saenz Julienne > --- > > Changes since RFC: > - Rebased to v5.4-rc6, fixed arm64 code. > > NOTE: This will only apply to linux-next, where missing end of the sentence. But only applying to linux-next isn't going to help anyone.. > diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c > index 45c00a54909c..f716ea634804 100644 > --- a/arch/arm64/mm/init.c > +++ b/arch/arm64/mm/init.c > @@ -20,6 +20,7 @@ > #include > #include > #include > +#include > #include > #include > #include > @@ -41,6 +42,8 @@ > #include > #include > > +#define ARM64_ZONE_DMA_BITS 30 > + > /* > * We need to be able to catch inadvertent references to memstart_addr > * that occur (potentially in generic code) before arm64_memblock_init() > @@ -424,6 +427,8 @@ void __init arm64_memblock_init(void) > else > arm64_dma_phys_limit = PHYS_MASK + 1; > > + zone_dma_bits = ARM64_ZONE_DMA_BITS; > + > reserve_crashkernel(); This actually adds a new limit, as there wasn't one before for arm64.