From: Greg Ungerer <gerg@linux-m68k.org>
To: Nicolas Pitre <nicolas.pitre@linaro.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
David Howells <dhowells@redhat.com>
Subject: Re: [PULL REQUEST] [PATCH v2 00/10] allow BFLT executables on systems with a MMU
Date: Tue, 19 Jul 2016 17:21:30 +1000 [thread overview]
Message-ID: <6b75e7a0-e181-08da-5013-315f6c45f02a@linux-m68k.org> (raw)
In-Reply-To: <1468812716-30537-1-git-send-email-nicolas.pitre@linaro.org>
Hi Nicolas,
On 18/07/16 13:31, Nicolas Pitre wrote:
> This series provides the necessary changes to allow "flat" executable
> binaries meant for no-MMU systems to actually run on systems with a MMU.
>
> This can also be found in the following git repo:
>
> git://git.linaro.org/people/nicolas.pitre/linux binfmt_flat_with_mmu
>
> *Why?*
>
> Because developing and testing natively on a large system with lots of
> RAM makes it so much more convenient to use all the existing profiling
> tools and debugging facilities that a kernel with lots of RAM can give.
> And incidentally, those systems with lots of RAM all have a MMU.
>
> *Why not use elf_fdpic?*
>
> The flat executable format is simple with very small footprint
> overhead, either in the executables themselves or kernel support.
> This makes the flat format more suitable than elf_fdpic for very small
> single-user-app embedded systems.
>
> And while elf_fdpic binaries can run on MMU systems, flat binaries still
> couldn't, which just felt wrong.
>
> So here it is. The no-MMU support should remain unaffected. Please consider
> for pulling.
>
> Tested on ARM only with a busybox build.
Tested on m68k (ColdFire specifically) and everything compiles
cleanly and works as before.
I tried running a flat binary on an MMU ColdFire system and
that crashed out with a SIGSEGV. I haven't debugged any further
than that yet.
I had a look over the patches and I didn't see any specific
problems. So from me:
Reviewed-by: Greg Ungerer <gerg@linux-m68k.org>
When I get a minute I'll dig a little into that bflat running
on MMU problem on ColdFire.
Regards
Greg
> Changes since v1:
>
> - Removed SuperH and Xtensa from the Kconfig rule as they fail to build
> due to lack of get/put_unaligned_user().
>
> - Clarified some commit logs a bit.
>
> diffstat:
>
> arch/arm/include/asm/flat.h | 5 +-
> arch/m68k/include/asm/flat.h | 5 +-
> fs/Kconfig.binfmt | 3 +-
> fs/binfmt_elf_fdpic.c | 38 +---
> fs/binfmt_flat.c | 372 +++++++++++++++++++++--------------
> fs/exec.c | 33 ++++
> include/linux/binfmts.h | 2 +
> 7 files changed, 268 insertions(+), 190 deletions(-)
>
>
prev parent reply other threads:[~2016-07-19 7:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 3:31 Nicolas Pitre
2016-07-18 3:31 ` [PATCH v2 01/10] binfmt_flat: assorted cleanups Nicolas Pitre
2016-07-19 4:52 ` Greg Ungerer
2016-07-19 6:40 ` Geert Uytterhoeven
2016-07-20 4:09 ` Nicolas Pitre
2016-07-20 6:54 ` Geert Uytterhoeven
2016-07-20 7:18 ` Greg Ungerer
2016-07-18 3:31 ` [PATCH v2 02/10] elf_fdpic_transfer_args_to_stack(): make it generic Nicolas Pitre
2016-07-18 3:31 ` [PATCH v2 03/10] binfmt_flat: use generic transfer_args_to_stack() Nicolas Pitre
2016-07-18 3:31 ` [PATCH v2 04/10] binfmt_flat: clean up create_flat_tables() and stack accesses Nicolas Pitre
2016-07-18 3:31 ` [PATCH v2 05/10] binfmt_flat: use proper user space accessors with relocs processing code Nicolas Pitre
2016-07-18 3:31 ` [PATCH v2 06/10] binfmt_flat: use proper user space accessors with old relocs code Nicolas Pitre
2016-07-18 3:31 ` [PATCH v2 07/10] binfmt_flat: use clear_user() rather than memset() to clear .bss Nicolas Pitre
2016-07-18 3:31 ` [PATCH v2 08/10] binfmt_flat: update libraries' data segment pointer with userspace accessors Nicolas Pitre
2016-07-18 3:31 ` [PATCH v2 09/10] binfmt_flat: add MMU-specific support Nicolas Pitre
2016-07-18 3:31 ` [PATCH v2 10/10] binfmt_flat: allow compressed flat binary format to work on MMU systems Nicolas Pitre
2016-07-18 11:47 ` One Thousand Gnomes
2016-07-18 15:45 ` Nicolas Pitre
2016-07-18 16:51 ` One Thousand Gnomes
2016-07-18 16:58 ` Nicolas Pitre
2016-07-19 7:21 ` Greg Ungerer [this message]
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=6b75e7a0-e181-08da-5013-315f6c45f02a@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=viro@zeniv.linux.org.uk \
/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®