From: Greg Ungerer <gerg@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rich Felker <dalias@libc.org>
Subject: Re: [PATCH 4/4] m68knommu: allow elf_fdpic loader to be selected
Date: Thu, 28 Apr 2022 23:41:17 +1000 [thread overview]
Message-ID: <99adb257-bf94-a291-b5a9-d22e97ce967a@linux-m68k.org> (raw)
In-Reply-To: <CAMuHMdXtj+ncYOhc3GcNdBuWxMe+0rP1aYCEKMP0yL3aJ_WH3w@mail.gmail.com>
Hi Geert,
On 28/4/22 17:20, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Thu, Apr 28, 2022 at 7:05 AM Greg Ungerer <gerg@linux-m68k.org> wrote:
>> The m68k architecture code is capable of supporting the binfmt_elf_fdpic
>> loader, so allow it to be configured. It is restricted to nommu
>> configurations at this time due to the MMU context structures/code not
>> supporting everything elf_fdpic needs when MMU is enabled.
>>
>> Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
>
> Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
>
>> --- a/fs/Kconfig.binfmt
>> +++ b/fs/Kconfig.binfmt
>> @@ -58,7 +58,7 @@ config ARCH_USE_GNU_PROPERTY
>> config BINFMT_ELF_FDPIC
>> bool "Kernel support for FDPIC ELF binaries"
>> default y if !BINFMT_ELF
>> - depends on (ARM || (SUPERH && !MMU))
>> + depends on (ARM || ((M68K || SUPERH) && !MMU))
>
> While at it, you may want to drop the unneeded outer parentheses,
> as they make the expression harder to round, IMHO.
Sure thing, will do,
Regards
Greg
>> select ELFCORE
>> help
>> ELF FDPIC binaries are based on ELF, but allow the individual load
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
prev parent reply other threads:[~2022-04-28 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 3:33 [PATCH 0/4] m68knommu: add support for elf-fdpic Greg Ungerer
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 [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=99adb257-bf94-a291-b5a9-d22e97ce967a@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.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).