mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Eder Zulian <ezulian@redhat.com>
Cc: linux-riscv@lists.infradead.org, pjw@kernel.org,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: mm: Move dma_contiguous_reserve() after NUMA initialization
Date: Tue, 21 Jul 2026 23:50:07 +0000	[thread overview]
Message-ID: <178467780765.1167722.17403934449709324097.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260714185648.1082483-1-ezulian@redhat.com>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.org>:

On Tue, 14 Jul 2026 20:56:48 +0200 you 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"
> 
> [...]

Here is the summary with links:
  - riscv: mm: Move dma_contiguous_reserve() after NUMA initialization
    https://git.kernel.org/riscv/c/76e885f2b89d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-07-21 23:50 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
2026-07-21 23:50 ` patchwork-bot+linux-riscv [this message]

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=178467780765.1167722.17403934449709324097.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@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 \
    --cc=pjw@kernel.org \
    /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®