From: Ingo Molnar <mingo@kernel.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
keescook@chromium.org, akpm@linux-foundation.org, hpa@zytor.com,
heiko.carstens@de.ibm.com, benh@kernel.crashing.org,
mpe@ellerman.id.au, mmarek@suse.cz, rusty@rustcorp.com.au
Subject: Re: [PATCH 0/4] support for text-relative kallsyms table
Date: Wed, 20 Jan 2016 11:33:25 +0100 [thread overview]
Message-ID: <20160120103325.GA20197@gmail.com> (raw)
In-Reply-To: <1453280738-18721-1-git-send-email-ard.biesheuvel@linaro.org>
* Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> This implements text-relative kallsyms address tables. This was developed as
> part of my series to implement KASLR/CONFIG_RELOCATABLE for arm64, but I think
> it may be beneficial to other architectures as well, so I am presenting it as a
> separate series.
>
> The idea is that on 64-bit builds, it is rather wasteful to use absolute
> addressing for kernel symbols since they are all within a couple of MBs of each
> other. On top of that, the absolute addressing implies that, when the kernel is
> relocated at runtime, each address in the table needs to be fixed up
> individually.
>
> Since all section-relative addresses are already emitted relative to _text, it
> is quite straight-forward to record only the offset, and add the absolute
> address of _text at runtime when referring to the address table.
>
> The reduction ranges from around 250 KB uncompressed vmlinux size and 10 KB
> compressed size (s390) to 3 MB/500 KB for ppc64 (although, in the latter case,
> the reduction in uncompressed size is primarily __init data)
So since kallsyms is in unswappable kernel RAM, the uncompressed size reduction is
what we care about mostly. How much bootloader load times are impacted is a third
order concern.
IOW a nice change!
Thanks,
Ingo
next prev parent reply other threads:[~2016-01-20 10:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 9:05 [PATCH 0/4] support for text-relative kallsyms table Ard Biesheuvel
2016-01-20 9:05 ` [PATCH 1/4] kallsyms: add support for relative offsets in kallsyms address table Ard Biesheuvel
2016-01-20 19:13 ` Kees Cook
2016-01-20 9:05 ` [PATCH 2/4] powerpc: enable text relative kallsyms for ppc64 Ard Biesheuvel
2016-01-21 4:01 ` Michael Ellerman
2016-01-20 9:05 ` [PATCH 3/4] s390: enable text relative kallsyms for 64-bit targets Ard Biesheuvel
2016-01-20 9:43 ` Heiko Carstens
2016-01-20 10:04 ` Ard Biesheuvel
2016-01-20 10:17 ` Heiko Carstens
2016-01-20 10:18 ` Ard Biesheuvel
2016-01-20 9:05 ` [PATCH 4/4] x86_64: " Ard Biesheuvel
2016-01-20 19:12 ` Kees Cook
2016-01-20 10:33 ` Ingo Molnar [this message]
2016-01-20 11:50 ` [PATCH 0/4] support for text-relative kallsyms table Arnd Bergmann
2016-01-21 5:10 ` Rusty Russell
2016-01-21 6:45 ` Ard Biesheuvel
2016-01-21 8:32 ` Ard Biesheuvel
2016-01-27 3:46 ` Rusty Russell
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=20160120103325.GA20197@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=benh@kernel.crashing.org \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mmarek@suse.cz \
--cc=mpe@ellerman.id.au \
--cc=rusty@rustcorp.com.au \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).