From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Cc: sam@ravnborg.org, x86@kernel.org, linux-kbuild@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/6] kbuild: Remove relocations from kallsyms table
Date: Tue, 18 Feb 2014 06:28:54 -0800 [thread overview]
Message-ID: <53036E26.1040701@zytor.com> (raw)
In-Reply-To: <1392733470-8228-2-git-send-email-andi@firstfloor.org>
On 02/18/2014 06:24 AM, Andi Kleen wrote:
> From: Andi Kleen <ak@linux.intel.com>
>
> Remove the ELF relocations from the kallsyms_address[] table.
> Instead we just store offsets to _text and relocate that while
> accessing the kallsyms table. This is done with a new
> kallsyms_offsets[] table. With these changes .tmp_kallsyms*.o
> becomes relocation free.
>
> In theory this would also allow to shrink the kallsyms table
> on 64bit by using offsets.
>
Why not do that, then?
-hpa
next prev parent reply other threads:[~2014-02-18 14:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 14:24 Single pass kallsyms v3 Andi Kleen
2014-02-18 14:24 ` [PATCH 1/6] kbuild: Remove relocations from kallsyms table Andi Kleen
2014-02-18 14:28 ` H. Peter Anvin [this message]
2014-02-18 18:50 ` Andi Kleen
2014-02-18 14:24 ` [PATCH 2/6] kbuild: Put kallsyms into own section Andi Kleen
2014-02-18 14:24 ` [PATCH 3/6] kbuild: Don't include const variable in kallsyms with !KALLSYMS_ALL Andi Kleen
2014-02-18 14:24 ` [PATCH 4/6] kbuild: Support padding in kallsyms tables v2 Andi Kleen
2014-02-18 14:24 ` [PATCH 5/6] kbuild: Use single pass kallsyms Andi Kleen
2014-02-18 14:24 ` [PATCH 6/6] kbuild: Remove .dot postfixes in kallsyms Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2014-02-14 21:17 Updated single-pass kallsyms patchkit for LTO Andi Kleen
2014-02-14 21:17 ` [PATCH 1/6] kbuild: Remove relocations from kallsyms table Andi Kleen
2014-02-08 7:50 Andi Kleen
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=53036E26.1040701@zytor.com \
--to=hpa@zytor.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--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