From: "Sunnanyong (Nanyong Sun, Intelligent Computing Solution Development Dep)" <sunnanyong@huawei.com>
To: <paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
<aou@eecs.berkeley.edu>, <anup.patel@wdc.com>
Cc: <linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<palmerdabbelt@google.com>, <atish.patra@wdc.com>,
<wangkefeng.wang@huawei.com>
Subject: Re: [PATCH -next] riscv: mm: remove redundant trampoline PGD for 64bit
Date: Thu, 17 Jun 2021 17:38:27 +0800 [thread overview]
Message-ID: <a58c4cde-6212-29f3-080a-f4e50221db21@huawei.com> (raw)
In-Reply-To: <20210527144819.12101-1-sunnanyong@huawei.com>
On 2021/5/27 22:48, Nanyong Sun wrote:
> Remove redundant trampoline PGD for 64bit and add more comment
> for why 32bit systems need trampoline PGD.
>
> There was a patch and discussion similar to this,refer to
> the link [1][2].
>
> The trampoline PGD is redundant for 64bit systems because:
> 1. The early PGD covers the entire kernel mapping. Directly
> loading early PGD can achieve the result in boot stage.
> A more trampoline PGD makes code hard to understand.
> 2. Directly loading early PGD is safe in 64bit systems since
> the kernel virtual address starts as 0xFFFFxxxxxxxxxxxx,
> which has a very big gap with RAM address.It won't fall into
> the corner case that 32bit system worrys.
> 3. Remove redundant trampoline PGD can benefit to code maintaince,
> because 64bit systems have more page table levels.For example:
> If we want to support SV48 which has 4 page table levels, we have
> to add a trampoline_pud and insert it before trampoline_pmd.
>
> Reference link:
> [1]https://lore.kernel.org/linux-riscv/20190325092234.5451-4-anup.patel@wdc.com/
> [2]https://lkml.org/lkml/2019/3/28/147
Long time no response.
Hi anup,
do you agree this?
next prev parent reply other threads:[~2021-06-17 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 14:48 Nanyong Sun
2021-06-17 9:38 ` Sunnanyong (Nanyong Sun, Intelligent Computing Solution Development Dep) [this message]
2021-06-29 13:01 ` Alex Ghiti
2021-07-28 3:09 ` Sunnanyong (Nanyong Sun, Intelligent Computing Solution Development Dep)
2021-07-28 6:25 ` Alex Ghiti
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=a58c4cde-6212-29f3-080a-f4e50221db21@huawei.com \
--to=sunnanyong@huawei.com \
--cc=anup.patel@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmerdabbelt@google.com \
--cc=paul.walmsley@sifive.com \
--cc=wangkefeng.wang@huawei.com \
/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®