From: patchwork-bot+linux-riscv@kernel.org
To: Vivian Wang <wangruikang@iscas.ac.cn>
Cc: linux-riscv@lists.infradead.org, pjw@kernel.org,
palmer@dabbelt.com, alex@ghiti.fr, linux-kernel@vger.kernel.org,
sophgo@lists.linux.dev, stable@vger.kernel.org,
gaohan@iscas.ac.cn
Subject: Re: [PATCH 0/2] riscv: mm: Define DIRECT_MAP_PHYSMEM_END, fix ZONE_DEVICE
Date: Fri, 03 Apr 2026 18:30:22 +0000 [thread overview]
Message-ID: <177524102228.1406513.593562525700646994.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260309-riscv-sparsemem-vmemmap-limits-v1-0-f40efe18e3cd@iscas.ac.cn>
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.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-04-03 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 11:09 [PATCH 0/2] riscv: mm: Define DIRECT_MAP_PHYSMEM_END, fix ZONE_DEVICE Vivian Wang
2026-03-09 11:09 ` [PATCH 2/2] riscv: mm: Define DIRECT_MAP_PHYSMEM_END Vivian Wang
2026-04-03 18:30 ` 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=177524102228.1406513.593562525700646994.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=gaohan@iscas.ac.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=sophgo@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=wangruikang@iscas.ac.cn \
/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