Re: [PATCH 0/2] riscv: mm: Define DIRECT_MAP_PHYSMEM_END, fix ZONE_DEVICE

patchwork-bot+linux-riscv
2026-04-03T18:30:40Z

Hello:

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

On Mon, 09 Mar 2026 19:09:36 +0800 you wrote:
> With HSA_AMD_SVM=y, RISC-V runs into the same problem as arm64 at one
> point did [1], where it tries to use a struct page that is outside of
> vmemmap. See log near the end.
>
> On RISC-V, the actual mappable range of physical addresses is dependent
> on the current MMU mode i.e. satp_mode. Define DIRECT_MAP_PHYSMEM_END to
> expose this information to get_free_mem_region().
>
> [...]

Here is the summary with links:
- [1/2] riscv: mm: WARN_ON() for bad addresses in vmemmap_populate()
https://git.kernel.org/riscv/c/49a5cb2dc86c
- [2/2] riscv: mm: Define DIRECT_MAP_PHYSMEM_END
(no matching commit)

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.