From: Fredrik Noring <noring@nocrew.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org, "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [RFC] MIPS: Align vmlinuz load address to a page boundary
Date: Mon, 2 Jul 2018 20:24:54 +0200 [thread overview]
Message-ID: <20180702182453.GA2537@localhost.localdomain> (raw)
In-Reply-To: <20180702131158.GA431230@linux-mips.org>
Hi Ralf,
On Mon, Jul 02, 2018 at 03:11:58PM +0200, Ralf Baechle wrote:
> Basically MIPS supports page sizes 4k, 8k, 16k, 32k, 64k. Not every system
> supports all page sizes. 4k is the safe bet while larger systems prefer 16k
> or 64k. Details are complicated.
>
> And of course with kexec the kexecing and the kexecuted kernels do not even
> have to have the same page size. It would appear that the userland code you
> were refering to in your 2nd email in
>
> https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/tree/kexec/kexec.c?id=HEAD#n343
>
> might erroneously fail if pagesize on the kexecing kernel is larger than of
> the kernel being kexed.
The comment in kexec.c suggests that it might be possible to find a way to
"cope with this problem". What could that mean? It came with the initial
commit, so the log is unfortunately not informative.
If we align vmlinuz to 64 KiB then it will work on all systems, I suppose.
Would there be drawbacks? Can the kernel make use of all memory regardless
of its base address, for example?
Fredrik
prev parent reply other threads:[~2018-07-02 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-10 18:20 [RFC] MIPS: Align vmlinuz load address to a page boundary Fredrik Noring
2018-06-12 18:19 ` Fredrik Noring
2018-07-02 13:11 ` Ralf Baechle
2018-07-02 18:24 ` Fredrik Noring [this message]
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=20180702182453.GA2537@localhost.localdomain \
--to=noring@nocrew.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.