From: Andrew Morton <akpm@linux-foundation.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] elf: init pt_regs pointer later
Date: Fri, 19 Apr 2019 13:08:26 -0700 [thread overview]
Message-ID: <20190419130826.849441bb8f526c9defcb1c0f@linux-foundation.org> (raw)
In-Reply-To: <20190419200343.GA19788@avx2>
On Fri, 19 Apr 2019 23:03:43 +0300 Alexey Dobriyan <adobriyan@gmail.com> wrote:
> Get "current_pt_regs" pointer right before usage.
>
> Space savings on x86_64:
>
> add/remove: 0/0 grow/shrink: 0/1 up/down: 0/-180 (-180)
> Function old new delta
> load_elf_binary 5806 5626 -180 !!!
-256 bytes with my setup.
> --- a/fs/binfmt_elf.c
> +++ b/fs/binfmt_elf.c
> @@ -704,12 +704,12 @@ static int load_elf_binary(struct linux_binprm *bprm)
> unsigned long start_code, end_code, start_data, end_data;
> unsigned long reloc_func_desc __maybe_unused = 0;
> int executable_stack = EXSTACK_DEFAULT;
> - struct pt_regs *regs = current_pt_regs();
> struct {
> struct elfhdr elf_ex;
> struct elfhdr interp_elf_ex;
> } *loc;
> struct arch_elf_state arch_state = INIT_ARCH_ELF_STATE;
> + struct pt_regs *regs;
>
> loc = kmalloc(sizeof(*loc), GFP_KERNEL);
> if (!loc) {
> @@ -1159,6 +1159,7 @@ static int load_elf_binary(struct linux_binprm *bprm)
> MAP_FIXED | MAP_PRIVATE, 0);
> }
>
> + regs = current_pt_regs();
> #ifdef ELF_PLAT_INIT
> /*
> * The ABI may specify that certain registers be set up in special
Why the heck does this make such a difference?
next prev parent reply other threads:[~2019-04-19 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 20:03 Alexey Dobriyan
2019-04-19 20:08 ` Andrew Morton [this message]
2019-04-20 18:07 ` Alexey Dobriyan
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=20190419130826.849441bb8f526c9defcb1c0f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®