Patch "arm64: mm: Move zone_dma_bits initialization into zone_sizes_init()" has been added to the 5.10-stable tree
gregkh at linuxfoundation.org
gregkh at linuxfoundation.org
Sun Mar 7 15:25:44 GMT 2021
This is a note to let you know that I've just added the patch titled
arm64: mm: Move zone_dma_bits initialization into zone_sizes_init()
to the 5.10-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
arm64-mm-move-zone_dma_bits-initialization-into-zone_sizes_init.patch
and it can be found in the queue-5.10 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable at vger.kernel.org> know about it.
>From foo at baz Sun Mar 7 04:22:37 PM CET 2021
From: Jing Xiangfeng <jingxiangfeng at huawei.com>
Date: Wed, 3 Mar 2021 15:33:14 +0800
Subject: arm64: mm: Move zone_dma_bits initialization into zone_sizes_init()
To: <gregkh at linuxfoundation.org>, <catalin.marinas at arm.com>, <will at kernel.org>, <akpm at linux-foundation.org>, <nsaenzjulienne at suse.de>, <paul.walmsley at sifive.com>, <palmer at dabbelt.com>, <aou at eecs.berkeley.edu>, <rppt at kernel.org>, <lorenzo.pieralisi at arm.com>, <guohanjun at huawei.com>, <sudeep.holla at arm.com>, <rjw at rjwysocki.net>, <lenb at kernel.org>, <song.bao.hua at hisilicon.com>, <ardb at kernel.org>, <anshuman.khandual at arm.com>, <bhelgaas at google.com>, <guro at fb.com>, <robh+dt at kernel.org>
Cc: <stable at vger.kernel.org>, <linux-arm-kernel at lists.infradead.org>, <frowand.list at gmail.com>, <devicetree at vger.kernel.org>, <linux-kernel at vger.kernel.org>, <linux-mm at kvack.org>, <linux-riscv at lists.infradead.org>, <jingxiangfeng at huawei.com>, <wangkefeng.wang at huawei.com>, Jeremy Linton <jeremy.linton at arm.com>
Message-ID: <20210303073319.2215839-3-jingxiangfeng at huawei.com>
From: Nicolas Saenz Julienne <nsaenzjulienne at suse.de>
commit 9804f8c69b04a39d0ba41d19e6bdc6aa91c19725 upstream
zone_dma_bits's initialization happens earlier that it's actually
needed, in arm64_memblock_init(). So move it into the more suitable
zone_sizes_init().
Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne at suse.de>
Tested-by: Jeremy Linton <jeremy.linton at arm.com>
Link: https://lore.kernel.org/r/20201119175400.9995-3-nsaenzjulienne@suse.de
Signed-off-by: Catalin Marinas <catalin.marinas at arm.com>
Cc: <stable at vger.kernel.org>
Signed-off-by: Jing Xiangfeng <jingxiangfeng at huawei.com>
Signed-off-by: Greg Kroah-Hartman <gregkh at linuxfoundation.org>
---
arch/arm64/mm/init.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
--- a/arch/arm64/mm/init.c
+++ b/arch/arm64/mm/init.c
@@ -190,6 +190,8 @@ static void __init zone_sizes_init(unsig
unsigned long max_zone_pfns[MAX_NR_ZONES] = {0};
#ifdef CONFIG_ZONE_DMA
+ zone_dma_bits = ARM64_ZONE_DMA_BITS;
+ arm64_dma_phys_limit = max_zone_phys(zone_dma_bits);
max_zone_pfns[ZONE_DMA] = PFN_DOWN(arm64_dma_phys_limit);
#endif
#ifdef CONFIG_ZONE_DMA32
@@ -376,11 +378,6 @@ void __init arm64_memblock_init(void)
early_init_fdt_scan_reserved_mem();
- if (IS_ENABLED(CONFIG_ZONE_DMA)) {
- zone_dma_bits = ARM64_ZONE_DMA_BITS;
- arm64_dma_phys_limit = max_zone_phys(ARM64_ZONE_DMA_BITS);
- }
-
if (IS_ENABLED(CONFIG_ZONE_DMA32))
arm64_dma32_phys_limit = max_zone_phys(32);
else
Patches currently in stable-queue which might be from jingxiangfeng at huawei.com are
queue-5.10/of-unittest-add-test-for-of_dma_get_max_cpu_address.patch
queue-5.10/mm-remove-examples-from-enum-zone_type-comment.patch
queue-5.10/arm64-mm-set-zone_dma-size-based-on-devicetree-s-dma-ranges.patch
queue-5.10/of-address-introduce-of_dma_get_max_cpu_address.patch
queue-5.10/arm64-mm-move-zone_dma_bits-initialization-into-zone_sizes_init.patch
queue-5.10/arm64-mm-set-zone_dma-size-based-on-early-iort-scan.patch
queue-5.10/arm64-mm-move-reserve_crashkernel-into-mem_init.patch
More information about the linux-riscv
mailing list