From: Ingo Molnar <mingo@kernel.org>
To: Robert Richter <rric@kernel.org>
Cc: "Borislav Petkov" <bp@alien8.de>,
LKML <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Tony Luck" <tony.luck@intel.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Andy Lutomirski" <luto@amacapital.net>,
"Matt Fleming" <matt@codeblueprint.co.uk>,
"Jörg Rödel" <joro@8bytes.org>, "Jiri Kosina" <jkosina@suse.cz>,
"Jeff Mahoney" <jeffm@suse.com>, "Michal Hocko" <mhocko@suse.cz>,
"Vlastimil Babka" <vbabka@suse.cz>,
"Andre Przywara" <andre@andrep.de>,
"Andreas Herrmann" <herrmann.der.user@gmail.com>,
"Richard Weinberger" <richard@nod.at>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Andi Kleen" <andi@firstfloor.org>
Subject: Re: [PATCH] x86: Drop 32-bit support ... finally.
Date: Wed, 1 Apr 2015 13:58:03 +0200 [thread overview]
Message-ID: <20150401115803.GA20149@gmail.com> (raw)
In-Reply-To: <20150401085600.GG4201@rric.localhost>
* Robert Richter <rric@kernel.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@kernel.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
next prev parent reply other threads:[~2015-04-01 11:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 8:15 [PATCH] x86: Drop 32-bit support ... finally Borislav Petkov
2015-04-01 8:21 ` Borislav Petkov
2015-04-01 8:45 ` Ingo Molnar
2015-04-01 8:56 ` Robert Richter
2015-04-01 9:38 ` Robert Richter
2015-04-01 17:28 ` Andi Kleen
2015-04-01 11:58 ` Ingo Molnar [this message]
2015-04-01 14:41 ` One Thousand Gnomes
2015-04-01 15:41 ` Theodore Ts'o
2015-04-01 15:46 ` Luck, Tony
2015-04-01 15:50 ` Dave Jones
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=20150401115803.GA20149@gmail.com \
--to=mingo@kernel.org \
--cc=andi@firstfloor.org \
--cc=andre@andrep.de \
--cc=bp@alien8.de \
--cc=herrmann.der.user@gmail.com \
--cc=hpa@zytor.com \
--cc=jeffm@suse.com \
--cc=jkosina@suse.cz \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=matt@codeblueprint.co.uk \
--cc=mhocko@suse.cz \
--cc=peterz@infradead.org \
--cc=richard@nod.at \
--cc=rostedt@goodmis.org \
--cc=rric@kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/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).