From: Palmer Dabbelt <palmer@rivosinc.com>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Song Shuai <suagrfillet@gmail.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Alexandre Ghiti <alexghiti@rivosinc.com>
Subject: Re: [PATCH] riscv: Start of DRAM should at least be aligned on PMD size for the direct mapping
Date: Thu, 03 Aug 2023 07:45:25 -0700 [thread overview]
Message-ID: <169107392510.27633.6639433423515028183.b4-ty@rivosinc.com> (raw)
In-Reply-To: <20230704121837.248976-1-alexghiti@rivosinc.com>
On Tue, 04 Jul 2023 14:18:37 +0200, Alexandre Ghiti wrote:
> So that we do not end up mapping the whole linear mapping using 4K
> pages, which is slow at boot time, and also very likely at runtime.
>
> So make sure we align the start of DRAM on a PMD boundary.
>
>
Applied, thanks!
[1/1] riscv: Start of DRAM should at least be aligned on PMD size for the direct mapping
https://git.kernel.org/palmer/c/9d3e8e1ff0d8
Best regards,
--
Palmer Dabbelt <palmer@rivosinc.com>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-08-03 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 12:18 [PATCH] riscv: Start of DRAM should at least be aligned on PMD size for the direct mapping Alexandre Ghiti
2023-07-04 12:26 ` Conor Dooley
2023-07-04 13:16 ` Alexandre Ghiti
2023-07-05 10:19 ` Song Shuai
2023-07-06 17:05 ` Palmer Dabbelt
2023-07-11 10:51 ` Alexandre Ghiti
2023-08-03 14:45 ` Palmer Dabbelt [this message]
2023-08-03 15:10 ` 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=169107392510.27633.6639433423515028183.b4-ty@rivosinc.com \
--to=palmer@rivosinc.com \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=suagrfillet@gmail.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;
as well as URLs for NNTP newsgroup(s).