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:	Wed, 1 Apr 2015 13:58:03 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Robert Richter <rric@...nel.org>
Cc:	Borislav Petkov <bp@...en8.de>,
	LKML <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Tony Luck <tony.luck@...el.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Andy Lutomirski <luto@...capital.net>,
	Matt Fleming <matt@...eblueprint.co.uk>,
	Jörg Rödel <joro@...tes.org>,
	Jiri Kosina <jkosina@...e.cz>, Jeff Mahoney <jeffm@...e.com>,
	Michal Hocko <mhocko@...e.cz>,
	Vlastimil Babka <vbabka@...e.cz>,
	Andre Przywara <andre@...rep.de>,
	Andreas Herrmann <herrmann.der.user@...il.com>,
	Richard Weinberger <richard@....at>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andi Kleen <andi@...stfloor.org>
Subject: Re: [PATCH] x86: Drop 32-bit support ... finally.


* Robert Richter <rric@...nel.org> wrote:

> [...]
> 
> Though, I assume a discussion on this topic will at least take 1-2 
> years, so it's good to start with it now. Also, I really would like 
> to finally switch off and retire my K7 which still runs some 
> regression tests (will need to check the actual used kernel 
> version). It was a good time, but now I realize it's somehow over. 
> Considering this and apart from my concerns above:
> 
> Acked-by: Robert Richter <rric@...nel.org>

Yeah, and phasing out 32-bit support will make it easier to add the 
(inevitable) 128-bit support as well, lifting the ~18 exabytes memory 
limit. That will allow us to move the 64-bit code into 'bugfix only' 
legacy status.

We really don't want to have this unmaintainable mixture of:

	128-bit support
	 64-bit support (legacy mode)
	 32-bit support (compat mode)
	 16-bit support (vm86 mode)
	  8-bit support (UART mode)

... all in the same kernel! We want a cleaner, more maintainable 
structure:

	128-bit support
	 64-bit support (compat mode)

... which more closely resembles today's kernel.

Another related change I'd like to make is to drop !SMP support and to 
default the kernel build to 4096 CPUs, and to move lower CPU counts to 
under CONFIG_EXPERT=y. By the time the commit trickles through to 
distros 1000-4000 core phones will be commonplace, so we might as well 
start the transition today.

Thanks,

	Ingo
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ