From: Greg Ungerer <gerg@linux-m68k.org>
To: linux-m68k@vger.kernel.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
dalias@libc.org, Greg Ungerer <gerg@linux-m68k.org>
Subject: [PATCH 0/4] m68knommu: add support for elf-fdpic
Date: Thu, 28 Apr 2022 13:33:15 +1000 [thread overview]
Message-ID: <20220428033319.239341-1-gerg@linux-m68k.org> (raw)
Add support to the m68k architecture code for the elf-fdpic loader.
As of commit 1bde925d2354 ("fs/binfmt_elf_fdpic.c: provide NOMMU loader
for regular ELF binaries") it is possible to run normal ELF executables
on nommu systems. These are simple enough to generate and test - even
without actual elf-fdpic toolchain support.
A few minor changes are required to have everything in place, all on the
architecture code side. The largest required addition is minimal regset
support (for elf-fdpic core dumping), otherwise a couple of cleanups and
some definitions is all that is required.
Note that this is only supporting nommu mode on the m68k at this time.
Changes will be required to the mm_context_t type to support elf-fdpic
with MMU enabled on m68k.
Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
---
arch/m68k/include/asm/elf.h | 9 +++++
arch/m68k/include/asm/mmu.h | 4 --
arch/m68k/include/uapi/asm/ptrace.h | 5 +++
arch/m68k/kernel/ptrace.c | 58 ++++++++++++++++++++++++++++++++++++
fs/Kconfig.binfmt | 2 -
5 files changed, 74 insertions(+), 4 deletions(-)
next reply other threads:[~2022-04-28 3:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 3:33 Greg Ungerer [this message]
2022-04-28 3:33 ` [PATCH 1/4] m68knommu: use asm-generic/mmu.h for nommu setups Greg Ungerer
2022-04-28 7:16 ` Geert Uytterhoeven
2022-04-28 3:33 ` [PATCH 2/4] m68knommu: implement minimal regset support Greg Ungerer
2022-04-28 3:33 ` [PATCH 3/4] m68knommu: add definitions to support elf_fdpic program loader Greg Ungerer
2022-04-28 3:33 ` [PATCH 4/4] m68knommu: allow elf_fdpic loader to be selected Greg Ungerer
2022-04-28 7:20 ` Geert Uytterhoeven
2022-04-28 13:41 ` Greg Ungerer
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=20220428033319.239341-1-gerg@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=dalias@libc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).