From: Paul Walmsley <paul.walmsley@sifive.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Anup Patel <anup@brainfault.org>, Anup Patel <Anup.Patel@wdc.com>,
Palmer Dabbelt <palmer@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Atish Patra <Atish.Patra@wdc.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Christoph Hellwig <hch@infradead.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] RISC-V: Allow booting kernel from any 4KB aligned address
Date: Mon, 18 Mar 2019 09:12:55 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1903180906560.25529@viisi.sifive.com> (raw)
In-Reply-To: <20190318071829.GF21385@rapoport-lnx>
On Mon, 18 Mar 2019, Mike Rapoport wrote:
> On Sat, Mar 16, 2019 at 04:55:30AM +0530, Anup Patel wrote:
>
> > We started exploring ways to re-claim memory below kernel because
> > we are trying to get Linux working on Kendryte K210 board
> > (https://kendryte.com/). This board has dual-core 64bit RISC-V but it
> > only has 8MB RAM.
>
> Huh, 8MB of RAM is tough...
>
> It is possible to use the memory below the kernel, e.g x86-64 does that.
> But it is definitely a separate change and with such RAM diet using 4K
> pages seems unavoidable.
>
> I still have concern about using 4K pages whenever the load address is not
> 2M (4M) aligned. People tend to not pay enough attention to such details
> and they would load the kernel at an arbitrary address and get the
> performance hit.
>
> I think the default should remain as is and the ability to map the kernel
> with 4K pages (and use 4K aligned load address) should be a Kconfig option.
Agreed. That Kconfig parameter should also be default-off.
Only a small number of people will try to run RISC-V Linux on a Kendryte
board. That niche use-case shouldn't impact the much larger group of
people who will run Linux on more reasonably-sized systems. No one should
need to ask people to report their kernel load address whenever someone
reports a performance regression.
- Paul
next prev parent reply other threads:[~2019-03-18 16:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 22:08 [PATCH 0/3] Boot RISC-V " Anup Patel
2019-03-12 22:08 ` [PATCH 1/3] RISC-V: Add separate defconfig for 32bit systems Anup Patel
2019-04-09 16:44 ` Palmer Dabbelt
2019-04-10 6:09 ` Anup Patel
2019-04-10 17:13 ` Palmer Dabbelt
2019-03-12 22:08 ` [PATCH 2/3] RISC-V: Make setup_vm() independent of GCC code model Anup Patel
2019-03-13 18:15 ` Mike Rapoport
2019-04-09 16:47 ` Palmer Dabbelt
2019-04-10 4:10 ` Anup Patel
2019-03-12 22:08 ` [PATCH 3/3] RISC-V: Allow booting kernel from any 4KB aligned address Anup Patel
2019-03-13 18:31 ` Mike Rapoport
2019-03-13 21:06 ` Anup Patel
2019-03-14 6:53 ` Mike Rapoport
2019-03-14 17:58 ` Anup Patel
2019-03-15 15:58 ` Mike Rapoport
2019-03-15 16:17 ` Anup Patel
2019-03-15 16:22 ` Anup Patel
2019-03-15 23:25 ` Anup Patel
2019-03-18 7:18 ` Mike Rapoport
2019-03-18 13:16 ` Anup Patel
2019-03-18 16:27 ` Mike Rapoport
2019-03-18 16:12 ` Paul Walmsley [this message]
2019-04-10 12:45 ` Nick Kossifidis
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=alpine.DEB.2.21.9999.1903180906560.25529@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=Anup.Patel@wdc.com \
--cc=Atish.Patra@wdc.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=rppt@linux.ibm.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®