From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney.cavm@gmail.com>
Cc: linux-mips@linux-mips.org, Ben Hutchings <ben@decadent.org.uk>
Subject: Re: Single MIPS kernel
Date: Wed, 22 Oct 2014 21:20:19 +0200 [thread overview]
Message-ID: <20141022192018.GD12502@linux-mips.org> (raw)
In-Reply-To: <5447F155.60106@gmail.com>
On Wed, Oct 22, 2014 at 11:03:01AM -0700, David Daney wrote:
> There is another reason to have a relocatable kernel: The security people
> are starting to demand it so that they can randomize the load address.
That may work for some platforms - but in the MIPS world we still have to
deal with very claustrophobic systems which barely leave any space to
move a kernel around.
> This is the approach I was thinking of taking. There would be a small PIC
> wrapper that applied the relocations, and then passed control to the real
> entry point.
>
> We would have to be careful of the ex_table, as that is now sorted at build
> time. For that, we could go to the scheme used by x86, and have that
> addresses in the ex_table be relative, build time sorting is already working
> for x86 relocatable kernels.
That's probably more of an implementation detail. I'm more concerned about
the overall bloat. I think many embedded users are so addivted to benchmark
results that this going to make or break the whole scheme.
Ralf
next prev parent reply other threads:[~2014-10-22 19:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 8:34 Single MIPS kernel Ralf Baechle
2014-10-22 10:53 ` John Crispin
2014-10-22 17:36 ` Florian Fainelli
2014-10-22 17:56 ` David Daney
2014-10-22 19:05 ` Ralf Baechle
2014-10-22 19:19 ` Maciej W. Rozycki
2014-10-22 20:42 ` Ralf Baechle
2014-10-22 21:10 ` David Daney
2014-10-22 21:53 ` James Hogan
2014-10-22 21:53 ` James Hogan
2014-10-22 22:18 ` David Daney
2014-10-22 18:03 ` David Daney
2014-10-22 19:20 ` Ralf Baechle [this message]
2014-10-22 22:15 ` Ben Hutchings
2014-10-22 23:22 ` Ralf Baechle
2014-10-23 1:02 ` Ben Hutchings
2014-10-23 3:13 ` Joshua Kinard
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=20141022192018.GD12502@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ben@decadent.org.uk \
--cc=ddaney.cavm@gmail.com \
--cc=linux-mips@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox