LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jon Masters <jcm@redhat.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Olof Johansson <olof@lixom.net>
Cc: "agraf@suse.de" <agraf@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Will Deacon <Will.Deacon@arm.com>
Subject: Re: [PATCH] arm64: Enable CONFIG_COMPAT also for 64k page size
Date: Fri, 13 Mar 2015 00:44:43 -0400 [thread overview]
Message-ID: <55026B3B.8050507@redhat.com> (raw)
In-Reply-To: <20141205111455.GC28339@e104818-lin.cambridge.arm.com>
On 12/05/2014 06:14 AM, Catalin Marinas wrote:
> On Thu, Dec 04, 2014 at 09:15:12PM +0000, Olof Johansson wrote:
>> On Thu, Dec 4, 2014 at 7:46 AM, Alexander Graf <agraf@suse.de> wrote:
>>> With binutils 2.25 the default alignment for 32bit arm sections changed to
>>> have everything 64k aligned. Armv7 binaries built with this binutils version
>>> run successfully on an arm64 system.
>>>
>>> Since effectively there is now the chance to run armv7 code on arm64 even
>>> with 64k page size, it doesn't make sense to block people from enabling
>>> CONFIG_COMPAT on those configurations.
>>>
>>> Signed-off-by: Alexander Graf <agraf@suse.de>
>>> ---
>>> arch/arm64/Kconfig | 1 -
>>> 1 file changed, 1 deletion(-)
>>>
>>> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
>>> index 9532f8d..3cf4f238 100644
>>> --- a/arch/arm64/Kconfig
>>> +++ b/arch/arm64/Kconfig
>>> @@ -409,7 +409,6 @@ source "fs/Kconfig.binfmt"
>>>
>>> config COMPAT
>>> bool "Kernel support for 32-bit EL0"
>>> - depends on !ARM64_64K_PAGES
>>> select COMPAT_BINFMT_ELF
>>> select HAVE_UID16
>>> select OLD_SIGSUSPEND3
>>
>> This is hardly "compat". Sure, it's great to have a new binutils that
>> has larger alignment, but practically not a single existing binary
>> will work today if someone tries to do this.
>>
>> So, it seems very premature to take this off. At the very least
>> document it like Will requested, and make it depend on !ARM_64K_PAGES
>> || EXPERT.
>
> That would work for me. We need to be clear that most existing 32-bit
> binaries will fail.
Agreed. Btw we intend to ensure that a future Fedora mass rebuild
incorporates this change in alignment on 32-bit to allow 32-bit Fedora
userspace to exist inside a (32-bit personality) chroot on AArch64. This
will allow us to migrate to 64-bit native builders both for 32 and
64-bit in advance of the eventual plan for KVM based build guests.
Jon.
next prev parent reply other threads:[~2015-03-13 4:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 15:46 [PATCH] arm64: Enable CONFIG_COMPAT also for 64k page size Alexander Graf
2014-12-04 18:18 ` Laura Abbott
2014-12-04 18:20 ` Will Deacon
2014-12-04 23:37 ` Alexander Graf
2014-12-08 13:47 ` Michael Matz
2014-12-06 17:23 ` Alexander Graf
2014-12-08 10:10 ` Will Deacon
2014-12-08 10:47 ` Alexander Graf
2015-03-11 11:24 ` Alexander Graf
2015-03-11 12:43 ` Andreas Schwab
2015-03-11 12:47 ` Arnd Bergmann
2015-03-11 13:08 ` Alexander Graf
2015-03-11 13:35 ` Andreas Schwab
2015-03-11 13:51 ` Arnd Bergmann
2015-03-11 13:57 ` Andreas Schwab
2015-03-11 15:44 ` Alexander Graf
2015-03-11 16:09 ` Andreas Schwab
2015-03-11 18:11 ` Alexander Graf
2015-03-12 9:07 ` [PATCH] arm64: fix implementation of mmap2 compat syscall Andreas Schwab
2015-03-16 14:16 ` [PATCH] arm64: Enable CONFIG_COMPAT also for 64k page size Christopher Covington
2015-03-16 14:19 ` Arnd Bergmann
2014-12-04 21:15 ` Olof Johansson
2014-12-04 23:41 ` Alexander Graf
2014-12-04 23:48 ` Olof Johansson
2014-12-05 10:39 ` Arnd Bergmann
2014-12-05 11:05 ` Catalin Marinas
2014-12-05 12:24 ` Arnd Bergmann
2014-12-05 12:31 ` Catalin Marinas
2015-02-18 13:40 ` Christopher Covington
2014-12-05 12:06 ` Alexander Graf
2014-12-05 11:14 ` Catalin Marinas
2014-12-05 11:35 ` Will Deacon
2015-03-13 4:44 ` Jon Masters [this message]
2014-12-05 16:35 ` Liviu Dudau
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=55026B3B.8050507@redhat.com \
--to=jcm@redhat.com \
--cc=Will.Deacon@arm.com \
--cc=agraf@suse.de \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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).