From: Josh Triplett <josh@joshtriplett.org>
To: Riku Voipio <riku.voipio@linaro.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH v2] uselib: default depending if libc5 was used
Date: Fri, 27 Nov 2015 12:07:10 -0800 [thread overview]
Message-ID: <20151127200710.GB17820@x> (raw)
In-Reply-To: <1448622860-9689-1-git-send-email-riku.voipio@linaro.org>
On Fri, Nov 27, 2015 at 01:14:20PM +0200, Riku Voipio wrote:
> uselib hasn't been used since libc5; glibc does not use it.
> Deprecate uselib a bit more, by making the default y only
> if libc5 was widely used on the plaform.
>
> This makes arm64 kernel built with defconfig slighly smaller
>
> bloat-o-meter:
> add/remove: 0/3 grow/shrink: 0/2 up/down: 0/-1390 (-1390)
> function old new delta
> kernel_config_data 18164 18162 -2
> uselib_flags 20 - -20
> padzero 216 192 -24
> sys_uselib 380 - -380
> load_elf_library 964 - -964
One question below.
> v2: Disable on X86_64 if no 32bit support
> init/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/init/Kconfig b/init/Kconfig
> index c24b6f7..a4bc657 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -285,7 +285,7 @@ config FHANDLE
>
> config USELIB
> bool "uselib syscall"
> - default y
> + def_bool ALPHA || M68K || SPARC || X86_32 || (X86_64 && IA32_EMULATION)
IA32_EMULATION depends on X86_64, so doesn't that reduce to:
def_bool ALPHA || M68K || SPARC || X86_32 || IA32_EMULATION
next prev parent reply other threads:[~2015-11-27 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 11:14 [PATCH v2] uselib: default depending if libc5 was used Riku Voipio
2015-11-27 20:07 ` Josh Triplett [this message]
2015-12-01 0:31 ` Andrew Morton
2015-12-01 1:06 ` Josh Triplett
2015-12-01 8:46 ` Geert Uytterhoeven
2015-12-01 12:35 ` Riku Voipio
2015-12-01 16:23 ` Josh Triplett
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=20151127200710.GB17820@x \
--to=josh@joshtriplett.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riku.voipio@linaro.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