From: Paul Walmsley <pjw@kernel.org>
To: Eder Zulian <ezulian@redhat.com>
Cc: pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: mm: Move dma_contiguous_reserve() after NUMA initialization
Date: Tue, 21 Jul 2026 17:00:58 -0600 (MDT) [thread overview]
Message-ID: <b446e77d-7e69-31c2-f438-555a61934198@kernel.org> (raw)
In-Reply-To: <20260714185648.1082483-1-ezulian@redhat.com>
Hi,
On Tue, 14 Jul 2026, Eder Zulian wrote:
> Move the dma_contiguous_reserve() call from setup_bootmem() to
> misc_mem_init(), placing it after arch_numa_init(). This ensures that
> NUMA topology is initialized when reserving contiguous memory for DMA.
>
> Tested with CMA_SIZE_PERNUMA enabled and two NUMA nodes on QEMU:
>
> qemu-system-riscv64 \
> -machine virt \
> -nographic \
> -smp 2 -m 512M \
> -numa node,nodeid=0,cpus=0,memdev=m0 \
> -numa node,nodeid=1,cpus=1,memdev=m1 \
> -object memory-backend-ram,id=m0,size=256M \
> -object memory-backend-ram,id=m1,size=256M \
> -kernel arch/riscv/boot/Image \
> -append "console=ttyS0 earlycon loglevel=7 cma=16M"
>
> Unpatched kernel's log (one global CMA pool and no per-nodepools, 16 MiB
> cma-reserved):
>
> [ 0.000000] cma: Reserved 16 MiB at 0x000000009ee00000
> ...
> [ 0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x000000008fffffff]
> [ 0.000000] Initmem setup node 1 [mem 0x0000000090000000-0x000000009fffffff]
> ...
> [ 0.056397] smp: Brought up 2 nodes, 2 CPUs
> [ 0.066135] Memory: 449288K/524288K available (12279K kernel code, 5980K rwdata, 6144K rodata, 2467K init, 482K bss, 54504K reserved, 16384K cma-reserved)
>
> Patched kernel's log (three CMA pools are created, 48 MiB total),
>
> [ 0.000000] cma: Reserved 16 MiB at 0x000000009ee00000
> [ 0.000000] cma: Reserved 16 MiB at 0x000000008ee00000
> [ 0.000000] cma: Reserved 16 MiB at 0x000000009de00000
> ...
> [ 0.054251] smp: Brought up 2 nodes, 2 CPUs
> [ 0.064082] Memory: 416520K/524288K available (12279K kernel code, 5980K rwdata, 6144K rodata, 2467K init, 482K bss, 54504K reserved, 49152K cma-reserved)
>
> Signed-off-by: Eder Zulian <ezulian@redhat.com>
Thanks, queued for v7.3.
- Paul
next prev parent reply other threads:[~2026-07-21 23:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 18:56 Eder Zulian
2026-07-21 23:00 ` Paul Walmsley [this message]
2026-07-21 23:50 ` patchwork-bot+linux-riscv
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=b446e77d-7e69-31c2-f438-555a61934198@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=ezulian@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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
all inboxes | Powered by JetHome®