From: Alexandre Ghiti <alex@ghiti.fr>
To: Vladimir Kondratiev <vladimir.kondratiev@mobileye.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] riscv: make ZONE_DMA32 optional
Date: Mon, 30 Sep 2024 11:55:28 +0200 [thread overview]
Message-ID: <e8f6ed93-d47c-4c07-963c-8f16f498abed@ghiti.fr> (raw)
In-Reply-To: <20240827113611.537302-1-vladimir.kondratiev@mobileye.com>
Hi Vladimir,
On 27/08/2024 13:36, Vladimir Kondratiev wrote:
> It is not necessary any RISCV platform has ZONE_DMA32.
>
> Example - if platform has no DRAM in [0..4G] region,
> it will report failure like below each boot.
>
> [ 0.088709] swapper/0: page allocation failure: order:7, mode:0xcc4(GFP_KERNEL|GFP_DMA32), nodemask=(null),cpuset=/
> [ 0.088832] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.11.0-rc5 #30
> [ 0.088864] Call Trace:
> [ 0.088869] [<ffffffff800059f2>] dump_backtrace+0x1c/0x24
> [ 0.088910] [<ffffffff805f328c>] show_stack+0x2c/0x38
> [ 0.088957] [<ffffffff805fd800>] dump_stack_lvl+0x52/0x74
> [ 0.088987] [<ffffffff805fd836>] dump_stack+0x14/0x1c
> [ 0.089010] [<ffffffff801a23a8>] warn_alloc+0xf4/0x176
> [ 0.089041] [<ffffffff801a3052>] __alloc_pages_noprof+0xc28/0xcb4
> [ 0.089067] [<ffffffff80086eda>] atomic_pool_expand+0x62/0x1f8
> [ 0.089090] [<ffffffff8080d674>] __dma_atomic_pool_init+0x46/0x9e
> [ 0.089115] [<ffffffff8080d762>] dma_atomic_pool_init+0x96/0x11c
> [ 0.089139] [<ffffffff80002146>] do_one_initcall+0x5c/0x1b2
> [ 0.089158] [<ffffffff8080127c>] kernel_init_freeable+0x214/0x274
> [ 0.089190] [<ffffffff805fefd8>] kernel_init+0x1e/0x10a
> [ 0.089209] [<ffffffff8060748a>] ret_from_fork+0xe/0x1c
>
> Signed-off-by: Vladimir Kondratiev <vladimir.kondratiev@mobileye.com>
> ---
> arch/riscv/Kconfig | 2 +-
> mm/Kconfig | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
> index 0f3cd7c3a436..94a573112625 100644
> --- a/arch/riscv/Kconfig
> +++ b/arch/riscv/Kconfig
> @@ -50,6 +50,7 @@ config RISCV
> select ARCH_HAS_TICK_BROADCAST if GENERIC_CLOCKEVENTS_BROADCAST
> select ARCH_HAS_UBSAN
> select ARCH_HAS_VDSO_DATA
> + select ARCH_HAS_ZONE_DMA_SET if 64BIT
> select ARCH_KEEP_MEMBLOCK if ACPI
> select ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE if 64BIT && MMU
> select ARCH_OPTIONAL_KERNEL_RWX if ARCH_HAS_STRICT_KERNEL_RWX
> @@ -200,7 +201,6 @@ config RISCV
> select THREAD_INFO_IN_TASK
> select TRACE_IRQFLAGS_SUPPORT
> select UACCESS_MEMCPY if !MMU
> - select ZONE_DMA32 if 64BIT
>
> config CLANG_SUPPORTS_DYNAMIC_FTRACE
> def_bool CC_IS_CLANG
> diff --git a/mm/Kconfig b/mm/Kconfig
> index b72e7d040f78..97c85da98e89 100644
> --- a/mm/Kconfig
> +++ b/mm/Kconfig
> @@ -1032,7 +1032,7 @@ config ZONE_DMA
> config ZONE_DMA32
> bool "Support DMA32 zone" if ARCH_HAS_ZONE_DMA_SET
> depends on !X86_32
> - default y if ARM64
> + default y if ARM64 || (RISCV && 64BIT)
>
> config ZONE_DEVICE
> bool "Device memory (pmem, HMM, etc...) hotplug support"
I'm wondering how distro kernels will deal with that since some
platforms will need the ZONE_DMA32 and some others will break when
enabled as you have shown.
Is there a way to make it optional at runtime instead?
Thanks,
Alex
next prev parent reply other threads:[~2024-09-30 9:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 11:36 Vladimir Kondratiev
2024-08-27 23:10 ` Drew Fustini
2024-09-20 8:58 ` Palmer Dabbelt
2024-09-20 13:18 ` Drew Fustini
2024-09-23 9:46 ` Ben Dooks
2024-09-20 14:04 ` Christoph Hellwig
2024-09-22 10:06 ` Vladimir Kondratiev
2024-09-24 6:39 ` Christoph Hellwig
2024-09-30 9:55 ` Alexandre Ghiti [this message]
2024-10-06 10:44 ` Vladimir Kondratiev
2024-10-06 10:55 ` [PATCH v1] " Vladimir Kondratiev
2024-10-06 22:58 ` Drew Fustini
2024-10-07 5:41 ` Christoph Hellwig
2024-10-07 6:17 ` Vladimir Kondratiev
2024-10-07 6:22 ` Christoph Hellwig
2024-10-07 11:39 ` Nick Kossifidis
2024-10-07 13:03 ` Vladimir Kondratiev
2024-10-07 12:17 ` [PATCH] " Ben Dooks
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=e8f6ed93-d47c-4c07-963c-8f16f498abed@ghiti.fr \
--to=alex@ghiti.fr \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=vladimir.kondratiev@mobileye.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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