Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 12 Dec 2018 10:48:14 +0000 (UTC)
From:   Thorsten Glaser <tg@mirbsd.de>
To:     Steven Newbury <steve@snewbury.org.uk>
cc:     "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        macro@linux-mips.org, luto@kernel.org, arnd@arndb.de,
        dalias@libc.org, s@ecloud.org, catalin.marinas@arm.com,
        fweimer@redhat.com, glaubitz@physik.fu-berlin.de,
        christian.brauner@canonical.com, hjl.tools@gmail.com, hpa@zytor.com
Subject: Re: Can we drop upstream Linux x32 support?
In-Reply-To: <1544605954.117529.27.camel@snewbury.org.uk>
Message-ID: <Pine.BSM.4.64L.1812121047070.21176@herc.mirbsd.org>
References: <1544605954.117529.27.camel@snewbury.org.uk>
Content-Language: de-DE-1901, en-GB
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=utf-8
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Steven Newbury dixit:

>I can't help but wonder if it wouldn't make more sense to drop x86
>support from long mode than x32.  AMD64 x86 support was always intended

Do you mean i386?

x86 = { i386, x32, amd64 }

No, please don’t. I use i386 as “companion architecture” to x32,
only the kernel and actually memory-hungry things (qemu) are
amd64 binaries on my system, and this works very well.

Thanks,
//mirabilos
-- 
18:47⎜<mirabilos:#!/bin/mksh> well channels… you see, I see everything in the
same window anyway      18:48⎜<xpt:#!/bin/mksh> i know, you have some kind of
telnet with automatic pong         18:48⎜<mirabilos:#!/bin/mksh> haha, yes :D
18:49⎜<mirabilos:#!/bin/mksh> though that's more tinyirc – sirc is more comfy