| Message ID | 20220428033319.239341-1-gerg@linux-m68k.org (mailing list archive) |
|---|---|
| Headers | show
Return-Path: <owner-linux-mm@kvack.org> X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 63038C433F5 for <linux-mm@archiver.kernel.org>; Thu, 28 Apr 2022 03:34:31 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 691F66B0071; Wed, 27 Apr 2022 23:34:30 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 641616B0072; Wed, 27 Apr 2022 23:34:30 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 508646B0073; Wed, 27 Apr 2022 23:34:30 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.28]) by kanga.kvack.org (Postfix) with ESMTP id 3F1F36B0071 for <linux-mm@kvack.org>; Wed, 27 Apr 2022 23:34:30 -0400 (EDT) Received: from smtpin29.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay12.hostedemail.com (Postfix) with ESMTP id 05C0F1216A6 for <linux-mm@kvack.org>; Thu, 28 Apr 2022 03:34:30 +0000 (UTC) X-FDA: 79404870300.29.7D2A70F Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by imf01.hostedemail.com (Postfix) with ESMTP id 7E97A4005E for <linux-mm@kvack.org>; Thu, 28 Apr 2022 03:34:24 +0000 (UTC) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 8343961A94; Thu, 28 Apr 2022 03:34:28 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8A27EC385A0; Thu, 28 Apr 2022 03:34:26 +0000 (UTC) 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 Message-Id: <20220428033319.239341-1-gerg@linux-m68k.org> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Stat-Signature: o8rd5ifrbhb96z1mh6bxazkbktjewnin X-Rspamd-Server: rspam07 X-Rspamd-Queue-Id: 7E97A4005E X-Rspam-User: Authentication-Results: imf01.hostedemail.com; dkim=none; spf=pass (imf01.hostedemail.com: domain of "SRS0=aK2k=VG=linux-m68k.org=gerg@kernel.org" designates 139.178.84.217 as permitted sender) smtp.mailfrom="SRS0=aK2k=VG=linux-m68k.org=gerg@kernel.org"; dmarc=none X-HE-Tag: 1651116864-190555 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: <linux-mm.kvack.org> |
| Series | m68knommu: add support for elf-fdpic | expand |
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(-)