[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161205151018.GD14429@e104818-lin.cambridge.arm.com>
Date: Mon, 5 Dec 2016 15:10:19 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: Yury Norov <ynorov@...iumnetworks.com>
Cc: arnd@...db.de, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
linux-arch@...r.kernel.org, szabolcs.nagy@....com,
heiko.carstens@...ibm.com, cmetcalf@...hip.com,
philipp.tomsich@...obroma-systems.com, joseph@...esourcery.com,
zhouchengming1@...wei.com, Prasun.Kapoor@...iumnetworks.com,
agraf@...e.de, geert@...ux-m68k.org, kilobyte@...band.pl,
manuel.montezelo@...il.com, pinskia@...il.com,
linyongting@...wei.com, klimov.linux@...il.com, broonie@...nel.org,
bamvor.zhangjian@...wei.com, maxim.kuvyrkov@...aro.org,
Nathan_Lynch@...tor.com, schwidefsky@...ibm.com,
davem@...emloft.net, christoph.muellner@...obroma-systems.com
Subject: Re: [PATCH 09/18] arm64: introduce binfmt_elf32.c
On Fri, Oct 21, 2016 at 11:33:08PM +0300, Yury Norov wrote:
> As we support more than one compat formats, it looks more reasonable
> to not use fs/compat_binfmt.c. Custom binfmt_elf32.c allows to move aarch32
> specific definitions there and make code more maintainable and readable.
Can you remind me why we need this patch (rather than using the default
fs/compat_binfmt_elf.c which you include here anyway)?
> --- /dev/null
> +++ b/arch/arm64/kernel/binfmt_elf32.c
> @@ -0,0 +1,31 @@
> +/*
> + * Support for AArch32 Linux ELF binaries.
> + */
> +
> +/* AArch32 EABI. */
> +#define EF_ARM_EABI_MASK 0xff000000
> +
> +#define compat_start_thread compat_start_thread
> +#define COMPAT_SET_PERSONALITY(ex) \
> +do { \
> + clear_thread_flag(TIF_32BIT_AARCH64); \
> + set_thread_flag(TIF_32BIT); \
> +} while (0)
You introduce this here but it seems to still be present in asm/elf.h.
--
Catalin
Powered by blists - more mailing lists