From: "Björn Töpel" <bjorn@kernel.org>
To: Chunyan Zhang <zhangchunyan@iscas.ac.cn>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Paul Walmsley <paul.walmsley@sifive.com>,
Alexandre Ghiti <alex@ghiti.fr>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Chunyan Zhang <zhang.lyra@gmail.com>,
Alistair Popple <apopple@nvidia.com>,
linux-mm@kvack.org
Subject: Re: [PATCH V5 1/3] riscv: mm: Prepare for reusing PTE RSW bit(9)
Date: Thu, 30 Jan 2025 09:42:21 +0100 [thread overview]
Message-ID: <87frl0snf6.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <20241113095833.1805746-2-zhangchunyan@iscas.ac.cn>
Chunyan Zhang <zhangchunyan@iscas.ac.cn> writes:
> The PTE bit(9) on RISC-V is reserved for software, it is used by devmap
> now which has to be disabled if we want to use bit(9) for other features,
> since there's no more free PTE bit on RISC-V now.
>
> So to make ARCH_HAS_PTE_DEVMAP selectable, this patch uses it as
> the build condition of devmap definitions.
Heads-up: It seems like Alistair's series [1] that removes the devmap
PTE bit will most likely land in 6.15.
Björn
[1] https://lore.kernel.org/linux-mm/cover.11189864684e31260d1408779fac9db80122047b.1736488799.git-series.apopple@nvidia.com/
next parent reply other threads:[~2025-01-30 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241113095833.1805746-1-zhangchunyan@iscas.ac.cn>
[not found] ` <20241113095833.1805746-2-zhangchunyan@iscas.ac.cn>
2025-01-30 8:42 ` Björn Töpel [this message]
2025-02-05 0:19 ` [PATCH V5 1/3] riscv: mm: Prepare for reusing PTE RSW bit(9) Alistair Popple
2025-02-11 1:20 ` Chunyan Zhang
2025-02-11 4:01 ` Deepak Gupta
2025-02-11 8:05 ` Chunyan Zhang
2025-02-20 18:23 ` Deepak Gupta
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=87frl0snf6.fsf@all.your.base.are.belong.to.us \
--to=bjorn@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=apopple@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=zhang.lyra@gmail.com \
--cc=zhangchunyan@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