[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <C342B5CD-D1E2-4364-B99E-C85470A869BB@theobroma-systems.com>
Date: Wed, 15 Apr 2015 19:01:23 +0200
From: "Dr. Philipp Tomsich" <philipp.tomsich@...obroma-systems.com>
To: Catalin Marinas <catalin.marinas@....com>
Cc: Arnd Bergmann <arnd@...db.de>,
linux-arm-kernel@...ts.infradead.org,
Andreas Kraschitzer <andreas.kraschitzer@...obroma-systems.com>,
Benedikt Huber <benedikt.huber@...obroma-systems.com>,
"Pinski, Andrew" <Andrew.Pinski@...iumnetworks.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andrew Pinski <apinski@...ium.com>,
Kumar Sankaran <ksankaran@....com>,
Christoph Muellner <christoph.muellner@...obroma-systems.com>
Subject: Re: [PATCH v4 00/24] ILP32 for ARM64
> On 15 Apr 2015, at 17:38, Catalin Marinas <catalin.marinas@....com> wrote:
>
> On Wed, Apr 15, 2015 at 05:15:16PM +0200, Arnd Bergmann wrote:
>> On Wednesday 15 April 2015 11:01:54 Catalin Marinas wrote:
>>> On Wed, Apr 15, 2015 at 11:18:06AM +0200, Dr. Philipp Tomsich wrote:
>>>> We’ve run full systems (built from buildroot) consisting of ILP32 binaries
>>>> only (ok… admittedly gdb was an exception, as we haven’t fixed the fact
>>>> that someone has assumed sizeof(long) == 8 in some data-structure of
>>>> the AArch64 backend there) in our verification runs. In fact, it will be very
>>>> special classes of applications that will need a 64bit address-space.
>>>
>>> If we are to merge AArch64-ILP32, I'd like to see a full software stack,
>>> maybe a distro like Debian. Otherwise the kernel code will bit-rot (just
>>> like it regularly happens with big endian).
>>
>> I actually don't think this should be a prerequisite. We have too many
>> dependencies here, and as long as we are debating the exact ABI,
>> any work that gets put into a full distro support (other than openembedded
>> etc) would likely be wasted.
>
> I agree with this not being a prerequisite for merging ILP32 but at
> least a long term plan to do something beyond openembedded, once we
> agreed on the ABI and _upstreamed_ the kernel and glibc code. Those
> legacy applications will probably need more than glibc to run and it's
> likely that people will want to run them in a full AArch64 (LP64)
> environment. A simpler approach (to me, I'm not a distro person) would
> be to just provide additional ILP32 libs in a multi-lib arm64 distro
> like Debian rather than all the packages. As for the compiler, AFAIK
> aarch64-linux-gnu-* simply needs an option to build for ILP32.
We’ve had a PPA for Ubuntu 14.04 in the past that included glibc, ncurses,
termcap, zlib and a few others in a multiarch setup… this was used in the
field by customers and worked rather well.
One of the engineers in my team is currently working on carrying this forward
so we can use this for any Debian-based AArch64 distribution in the future.
Best,
Phil.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists