[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <FB9A08ED-7D37-44C1-86D1-25E3711E3837@amacapital.net>
Date: Sat, 15 Dec 2018 07:30:43 -0800
From: Andy Lutomirski <luto@...capital.net>
To: Thomas Schoebel-Theuer <tst@...oebel-theuer.de>
Cc: Andy Lutomirski <luto@...nel.org>, X86 ML <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux API <linux-api@...r.kernel.org>,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Borislav Petkov <bp@...en8.de>,
Florian Weimer <fweimer@...hat.com>,
Mike Frysinger <vapier@...too.org>,
"H. J. Lu" <hjl.tools@...il.com>, Rich Felker <dalias@...c.org>,
x32@...ldd.debian.org, Arnd Bergmann <arnd@...db.de>,
Will Deacon <will.deacon@....com>,
Catalin Marinas <catalin.marinas@....com>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Can we drop upstream Linux x32 support?
> On Dec 14, 2018, at 11:41 PM, Thomas Schoebel-Theuer <tst@...oebel-theuer.de> wrote:
>
>> On 12/14/18 22:41, Thomas Schöbel-Theuer wrote:
>>> On 12/14/18 22:24, Andy Lutomirski wrote:
>>>
>>> I'm talking about x32, which is a different beast.
>>>
>>
>> So from my viewpoint the mentioned roadmap / timing requirements will remain the same, whatever you are dropping.
>>
>> Enterprise-critical use cases will probably need to be migrated to KVM/qemu together with their old kernel versions, anyway (because the original hardware will be no longer available in a few decades).
>>
>
> Here is a systematic approach to the problem.
>
This is way off topic. Let’s not discuss it on this thread, please.
Powered by blists - more mailing lists