Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp25879imu; Fri, 14 Dec 2018 13:44:02 -0800 (PST) X-Google-Smtp-Source: AFSGD/X2JVDjIPe9QntLAhXj/ytERc+xTxbkeNPkOs3MHfrQgWxxNf8DBdQaNg2LbyeKqllrHoKn X-Received: by 2002:a63:6ac5:: with SMTP id f188mr945546pgc.165.1544823842776; Fri, 14 Dec 2018 13:44:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544823842; cv=none; d=google.com; s=arc-20160816; b=BpVDYi0JnSaKmSzlApISD4qX0rsE86BU5dBXgJ8vZV1lit55xf5KwXcgVXLz94y1jx OAH1dZwrHBLoevK0vxYPRvvRZNIZChO+yys85ra/YaIwJS0TXR7BgqmaDbdQLqjwO5hb wgZz1VzN1W3siAfEJHPFjpM3MBLkNNbttxxykCjMmmYOvabJPB9/otPCW0b96l+XteVp EOv5IdColTPDdUSQYm2UrSBkBYX3qH0+YvF2fRCJ6vZlffj0B603CbDkxw/tUnfz3Oh2 Bt1OADqbOuwsEd7sCy3zkxYnV3XeZ9ygOV5ZRxdvY2OUapGmD2hE9TS5Q4y7oCztAPUz Suxg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=bMSKCa/7E+BrBoPOgFkZPRw065Ro+f+aqWXPOfJWdFI=; b=JIc09lPt3evjub6x6m7fPLsj4V8BSlXKhGQvSHgfJqNXQrTDwmfaixpDqfiBPyYJFI PtH2zVcU7BgOPF+GuPB8sC4wUCFlZ4+FgHp+qtpZCkrhkWBE0XTUfpKcCcGd2a+q3sD+ GkRdnYvVikSwe8FsHeB0m3us2eNW0sNElg8oQNmw8oMZ/B16PAeDOgpwHMNLnh/oPXNB Dd6sXgOLlWmNcNMmXb1e5D1mYplqf8RPbMzHk7RbnTwxTyoE/KrFObci/7bWMfAxa++c 5XICAaY0PitEEczkD8XT+xYSd8Y+wJrOukNXNeVB45OQzMQbg1UBnY2Iw3k/Pg2xkgld pO7g== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@schoebel-theuer.de header.s=strato-dkim-0002 header.b=h96pvSO4; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q7si4725078pgl.303.2018.12.14.13.43.46; Fri, 14 Dec 2018 13:44:02 -0800 (PST) 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; Authentication-Results: mx.google.com; dkim=fail header.i=@schoebel-theuer.de header.s=strato-dkim-0002 header.b=h96pvSO4; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731193AbeLNVl1 (ORCPT + 99 others); Fri, 14 Dec 2018 16:41:27 -0500 Received: from mo4-p02-ob.smtp.rzone.de ([85.215.255.80]:15020 "EHLO mo4-p02-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730887AbeLNVl0 (ORCPT ); Fri, 14 Dec 2018 16:41:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1544823684; s=strato-dkim-0002; d=schoebel-theuer.de; h=In-Reply-To:Date:Message-ID:From:References:Cc:To:Subject: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=bMSKCa/7E+BrBoPOgFkZPRw065Ro+f+aqWXPOfJWdFI=; b=h96pvSO4SNe+lAbrrg8iBn4VPYG/vsZTUMGmvFZOTejlZ9muZ3+sjPV/QB4nA/qFnw vMec17syO1+nzzlbVdI8Uoh2tBUNvMMnq/BDdY1klB47NxoLNt4Ybh+xv+l2V+93P3gD Vh1IKVaZhrVO8LpPKouyzdSnClMl/bG+ls9eyfGRV9qCpZ5qjomOy22cV0Cy4p7+gcB7 UEBd4cs/2L7o4BpMoxcgPUcv3zNyp6iySgWjdtaqZkrWbSIGfIPrH/Tv808MsFfx9VpC o4Nk7OYi+wyE1Rcof3KX3ymXAv/eFcX8BoOhxQ52ODw7JrteCQQ/0sC6BoIpDb6I3mEr YNrw== X-RZG-AUTH: ":OH8QVVOrc/CP6za/qRmbF3BWedPGA1vjs2e0bDjfg8OiOrPJifeRMRhMbfKobJAvSmsJbFO0KIY=" X-RZG-CLASS-ID: mo00 Received: from [192.168.2.24] by smtp.strato.de (RZmta 44.8 DYNA|AUTH) with ESMTPSA id V03c59uBELfK6uQ (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate); Fri, 14 Dec 2018 22:41:20 +0100 (CET) Subject: Re: Can we drop upstream Linux x32 support? To: Andy Lutomirski Cc: X86 ML , LKML , Linux API , "H. Peter Anvin" , Peter Zijlstra , Borislav Petkov , Florian Weimer , Mike Frysinger , "H. J. Lu" , Rich Felker , x32@buildd.debian.org, Arnd Bergmann , Will Deacon , Catalin Marinas , Linus Torvalds References: <6577ac4f-524c-37f4-a4d0-6eb94ec7d9a5@schoebel-theuer.de> From: =?UTF-8?Q?Thomas_Sch=c3=b6bel-Theuer?= Message-ID: <35905587-2d7b-c0ab-e081-2b938d60e881@schoebel-theuer.de> Date: Fri, 14 Dec 2018 22:41:20 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/14/18 22:24, Andy Lutomirski wrote: > I should clarify again: I am not suggesting that we drop 32-bit > support in the forseeable future. (Well, I might eventually suggest > that we drop support for 32-bit *hardware* at some point, but not for > 32-bit compat software.) Linux's compat code is quite robust and is > even fairly maintainable. > > I'm talking about x32, which is a different beast. > OK, this does not really make a big difference for large-scale enterprise users. Some day in the very distant future any legacy system will disappear, eventually. 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).