From: Christoph Hellwig <hch@lst•de>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse•de>
Cc: linux-s390@vger•kernel.org, Vasily Gorbik <gor@linux•ibm.com>,
Will Deacon <will@kernel•org>,
Catalin Marinas <catalin.marinas@arm•com>,
linuxppc-dev@lists•ozlabs.org,
Heiko Carstens <heiko.carstens@de•ibm.com>,
linux-kernel@vger•kernel.org,
Christian Borntraeger <borntraeger@de•ibm.com>,
iommu@lists•linux-foundation.org,
Paul Mackerras <paulus@samba•org>,
Michael Ellerman <mpe@ellerman•id.au>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
Robin Murphy <robin.murphy@arm•com>,
Christoph Hellwig <hch@lst•de>,
linux-arm-kernel@lists•infradead.org,
Marek Szyprowski <m.szyprowski@samsung•com>
Subject: Re: [PATCH] dma/direct: turn ARCH_ZONE_DMA_BITS into a variable
Date: Thu, 31 Oct 2019 16:47:59 +0100 [thread overview]
Message-ID: <20191031154759.GA7162@lst.de> (raw)
In-Reply-To: <20191031152837.15253-1-nsaenzjulienne@suse.de>
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 <nsaenzjulienne@suse•de>
> ---
>
> 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 <linux/sort.h>
> #include <linux/of.h>
> #include <linux/of_fdt.h>
> +#include <linux/dma-direct.h>
> #include <linux/dma-mapping.h>
> #include <linux/dma-contiguous.h>
> #include <linux/efi.h>
> @@ -41,6 +42,8 @@
> #include <asm/tlb.h>
> #include <asm/alternative.h>
>
> +#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.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-31 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 15:28 [PATCH] dma/direct: turn ARCH_ZONE_DMA_BITS into a variable Nicolas Saenz Julienne
2019-10-31 15:47 ` Christoph Hellwig [this message]
2019-10-31 15:53 ` Nicolas Saenz Julienne
2019-10-31 15:57 ` Christoph Hellwig
2019-10-31 16:22 ` Nicolas Saenz Julienne
2019-10-31 16:58 ` Christoph Hellwig
2019-10-31 18:06 ` Catalin Marinas
2019-10-31 18:32 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191031154759.GA7162@lst.de \
--to=hch@lst$(echo .)de \
--cc=benh@kernel$(echo .)crashing.org \
--cc=borntraeger@de$(echo .)ibm.com \
--cc=catalin.marinas@arm$(echo .)com \
--cc=gor@linux$(echo .)ibm.com \
--cc=heiko.carstens@de$(echo .)ibm.com \
--cc=iommu@lists$(echo .)linux-foundation.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=m.szyprowski@samsung$(echo .)com \
--cc=mpe@ellerman$(echo .)id.au \
--cc=nsaenzjulienne@suse$(echo .)de \
--cc=paulus@samba$(echo .)org \
--cc=robin.murphy@arm$(echo .)com \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox