Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp11701imu; Fri, 14 Dec 2018 13:26:31 -0800 (PST) X-Google-Smtp-Source: AFSGD/VAgLH2PnSc5l5aACNzQ76fGiJQVJWyxMs161skh50wIZdwHnFjXnMNBZDQBDLcNyXViyPw X-Received: by 2002:a17:902:a601:: with SMTP id u1mr4347475plq.77.1544822791637; Fri, 14 Dec 2018 13:26:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544822791; cv=none; d=google.com; s=arc-20160816; b=gB5E8i7oBPiGW5+0EmEKUVhc+iRh/sSPPHTg0PIClXruvUjz/6+8JkfNUyK7msoMm1 WoARWR9aULzBT5uy43hHKfjZ4tNgpIpdKOdF+gRHJEQD+79NASny5mDRhAAqCQFGy9k8 FKlse8DR5rPS8Il9Yz2uoRR5CbgY/oSqfHrpo+pVenMucHOrC5UXfF3zkDsDZJ+lYONN vEDGtuj/R62rdmvbRu/6luu6k4t4DdM3diQeVDxOyZwbjVhmZI45p39ojU0x1SwzwD4b OyFDRem+IpUu+rz1AI9/CpXZCuAbSYiOwS+Q4O0eu68gy7OVW4W28EqqcaGjFzS6VRIP oX6w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=H26wYBMh6K51YXH4BF0+mtiSOaLZEZ7XVO/qGb7QY9U=; b=jhhzdo+qJo+gjkt2JxsIozbaCu05Qym0K05q1IpiOdUL3V12co9cV/O7MZE0PLVqrl /cdMWecq3Ix6ZMFshBx52KSQzXHTckjitrTAOtPvui1R6DPiGEgaCWz208LkflSSIqmT sxt2nbtsyYEIzLVTJ4V6zkdt0sXMfdhputD5BbF25xbjw8URjkvtWM7jf/cgefXDGUrX jXypsPEEwuwwsnmXxh4xfka/i7KPXr/GeSb9EmjF7GCtb4AucC/debbQ0BCX3YaJlKI+ AfKV6KyeH+grK4+ghfFHvYFEco2fah7I5Y70SbYpzAm13IWMmSZBsyYTZvcU9Y8OQ4fc TrMg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=YsP1y1fk; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b13si3821204pgw.472.2018.12.14.13.26.15; Fri, 14 Dec 2018 13:26:31 -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=pass header.i=@kernel.org header.s=default header.b=YsP1y1fk; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730990AbeLNVYn (ORCPT + 99 others); Fri, 14 Dec 2018 16:24:43 -0500 Received: from mail.kernel.org ([198.145.29.99]:34896 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730734AbeLNVYm (ORCPT ); Fri, 14 Dec 2018 16:24:42 -0500 Received: from mail-wr1-f54.google.com (mail-wr1-f54.google.com [209.85.221.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 443E52080F for ; Fri, 14 Dec 2018 21:24:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1544822682; bh=ekvsmSSSd58A4N1M0AKk5aYGsJQVH6wJr8GJVQFeMfI=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=YsP1y1fktr0nPP9Kp7LSnZKrCYPdZGXBWlQSzc4nooCMikLxLt1ARmTEZtlsBgcLz X/E+fJFrMMT51xZRdxf48o/RuNQx4qNXUQKgwjgw53nVMaTfYen6wDuyJCvWkIGQxa 7F+UXye2Ra28qLtfauOoTL1TBX9QQVfTQONH5xrk= Received: by mail-wr1-f54.google.com with SMTP id x10so6743252wrs.8 for ; Fri, 14 Dec 2018 13:24:41 -0800 (PST) X-Gm-Message-State: AA+aEWYE9lI79lo89iH/zmOQwIMm29EONl4ci4PySOXDulVTvBBNfQMK bMvMn7aabisDetvFCjFR8KNmx7Z7gwPigOmNy4CtqQ== X-Received: by 2002:adf:ea81:: with SMTP id s1mr3737192wrm.309.1544822680404; Fri, 14 Dec 2018 13:24:40 -0800 (PST) MIME-Version: 1.0 References: <6577ac4f-524c-37f4-a4d0-6eb94ec7d9a5@schoebel-theuer.de> In-Reply-To: <6577ac4f-524c-37f4-a4d0-6eb94ec7d9a5@schoebel-theuer.de> From: Andy Lutomirski Date: Fri, 14 Dec 2018 13:24:28 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Can we drop upstream Linux x32 support? To: thomas@schoebel-theuer.de Cc: Andrew Lutomirski , 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 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 14, 2018 at 1:22 PM Thomas Sch=C3=B6bel-Theuer wrote: > > On 12/11/18 02:23, Andy Lutomirski wrote: > > I'm seriously considering sending a patch to remove x32 support from > > upstream Linux. > > I am downstream maintainer of several self-patched kernels at 1&1 Ionos. > The kernels are rolled out to several tenthousands of production servers > running in several datacenters and in multiple continents. > > Currently, we have a few thousands of servers relying on 32bit ABIs in > some thousands of VMs and/or containers of various types (LXC, OpenVZ, et= c). 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.