From: Paul Walmsley <pjw@kernel.org>
To: Vivian Wang <wangruikang@iscas.ac.cn>
Cc: Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Alexandre Ghiti <alex@ghiti.fr>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
sophgo@lists.linux.dev, stable@vger.kernel.org,
Han Gao <gaohan@iscas.ac.cn>
Subject: Re: [PATCH 2/2] riscv: mm: Define DIRECT_MAP_PHYSMEM_END
Date: Thu, 4 Jun 2026 16:34:49 -0600 (MDT) [thread overview]
Message-ID: <533b4094-e97c-1661-1ad2-4e7aea683f4f@kernel.org> (raw)
In-Reply-To: <20260309-riscv-sparsemem-vmemmap-limits-v1-2-f40efe18e3cd@iscas.ac.cn>
On Mon, 9 Mar 2026, Vivian Wang wrote:
> On RISC-V, the actual mappable range of physical address space is
> dependent on the current MMU mode i.e. satp_mode (See
> Documentation/arch/riscv/vm-layout.rst).
>
> Define the DIRECT_MAP_PHYSMEM_END macro based on the existing virtual
> address space layout macros to expose this information to
> get_free_mem_region(). Otherwise, it returns a region that couldn't be
> mapped, which breaks ZONE_DEVICE.
>
> Cc: <stable@vger.kernel.org> # v6.13+
> Tested-by: Han Gao <gaohan@iscas.ac.cn> # SG2044
> Signed-off-by: Vivian Wang <wangruikang@iscas.ac.cn>
Thanks, queued for v7.2.
- Paul
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-06-04 22:35 UTC|newest]
Thread overview: 6+ 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 1/2] riscv: mm: WARN_ON() for bad addresses in vmemmap_populate() Vivian Wang
2026-03-25 23:11 ` Paul Walmsley
2026-03-09 11:09 ` [PATCH 2/2] riscv: mm: Define DIRECT_MAP_PHYSMEM_END Vivian Wang
2026-06-04 22:34 ` Paul Walmsley [this message]
2026-04-03 18:30 ` [PATCH 0/2] riscv: mm: Define DIRECT_MAP_PHYSMEM_END, fix ZONE_DEVICE 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=533b4094-e97c-1661-1ad2-4e7aea683f4f@kernel.org \
--to=pjw@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=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