linux-kernel - Re: Drop support for x86-32

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 24 Aug 2012 18:54:45 +0200
From:	Martin Nybo Andersen <tweek@...ek.dk>
To:	Chris Friesen <chris.friesen@...band.com>
Cc:	wbrana <wbrana@...il.com>,
	Bernd Petrovitsch <bernd@...rovitsch.priv.at>,
	Ondrej Zary <linux@...nbow-software.org>,
	"linux-kernel" <linux-kernel@...r.kernel.org>
Subject: Re: Drop support for x86-32

On Friday 24 August 2012 18:24:16 Chris Friesen wrote:
> On 08/24/2012 10:14 AM, Martin Nybo Andersen wrote:
> > (And I'm still not sure why one would run 32-bit applications on a 64-bit
> > architecture...)
> 
> There are several architectures (powerpc comes to mind) where 32-bit
> userspace on 64-bit kernel is the norm because it offers performance
> advantages due to the smaller pointer size if the process doesn' t need
> the larger address space.  This is the rationale behind the new x32 ABI
> for x86-64 kernels.

For specific cases surely a specific ABI will be faster than another, and 
because of that I love that we are free to choose when using Linux. Personally 
I'd hate maintaining up to three versions of the same userspace code, while 
other might need it (or even do it happily) -- but that is another story.

What I'd hate even more is rendering my old working hardware useless by 
removing x86-32 support from the kernel. To reason the removal by saying 
"Microsoft plans to do it" just makes me go bonkers...

> You might also want to run legacy apps (which can't be recompiled) on
> new hardware.

These legacy apps will most likely be compiled for x86-32 and not x32 (an 
argument for not removing x86-32 support on a running x86-64 kernel).

-- 
Cheers,
Martin
--
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/