Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3506919imu; Fri, 18 Jan 2019 11:36:13 -0800 (PST) X-Google-Smtp-Source: ALg8bN5xVSmuHQ6fEz2E4uQFF83LgOZMm2+vn29HvyM/e5ba0Yp687txqPCelwfTioNpQ9rCjU1g X-Received: by 2002:a62:1289:: with SMTP id 9mr20889252pfs.102.1547840173482; Fri, 18 Jan 2019 11:36:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547840173; cv=none; d=google.com; s=arc-20160816; b=L1+JqA71mDjimADGfQGvB9W1wifUO7f3dtPQxceaRPijIYE0ot5lwz789Fxa/e+a2f x01YXklDbPM1ga2gm+GPxAruhsVDlAOLVAmGZ2MORZVe3+7cNrKAKvB+06LQ6RjQ/1gt aBOnfvIN0v2uV5kGbSi1OXsM9uNlq+fPwSbXUMtpqBxbBG8pclZKIN0fq7AyKHunXoGr PKz520pvIFXRT1hjHNKwk7LTJsutsGhha6VboNPdhi7YoKJ1knSHFiriCHl0tpKg5SKu EPx5pp3j2cNCLwSt+0BYaxCzRJqh2X73P68tFG+0bs6Pr7wKIMFnuP/i9TRHyu6zypMG 72jw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version; bh=ErLXt+4MLir6MBRid1biQgec4eSYhQQBJKNsrW9q3Fs=; b=EzJJEqCAaWyv9XkExC/pxA7L9rZGS8vkv1zaKLxKCY8N29Uty0PIbdM6SjMawe7U1F A+6eysRyjExjQ9R8SkNhuhCc5Vp40DOKq0qLTyx3Ef3DFD09BuSrVayMj0LK2qQwD3g4 E7o27aI89H6deq4Vy0IkaT+cvXfgBLMF2FrzLJ3cBtorXo5KohU4D2WcwO/nuHiLh7cH SXl3P36s3MezwqDLVfyHM06fyKutV3sT9rlGguyA7oZJzrauCgUm6EvMCZzlkhZZN4+v FiBi699cnKQ6E3DYJoKH6gir0AEITAuW3fkrMQDkEtzdy/vwPtsU8GGb5P0agYTGciIx LvdA== ARC-Authentication-Results: i=1; mx.google.com; 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 ca6si5534781plb.141.2019.01.18.11.35.55; Fri, 18 Jan 2019 11:36:13 -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; 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 S1729354AbfARTdo (ORCPT + 99 others); Fri, 18 Jan 2019 14:33:44 -0500 Received: from mail-qt1-f196.google.com ([209.85.160.196]:33979 "EHLO mail-qt1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728738AbfARTdn (ORCPT ); Fri, 18 Jan 2019 14:33:43 -0500 Received: by mail-qt1-f196.google.com with SMTP id r14so16558949qtp.1; Fri, 18 Jan 2019 11:33:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ErLXt+4MLir6MBRid1biQgec4eSYhQQBJKNsrW9q3Fs=; b=Cu91HrP0wa9j0pLECqvB4NSoVGSq0QHevyvV5eLXyuuhdiAu8xRirAEalLNK8Z8ogG 7aUezEAzQW0MVrjVyf2TTo1BRdmfTCqn25TS6cBMsNQ+DIcUTeXtMjIPjnhJWVuYJac+ 20fJzLRFfYwKsCfQT6ao+iGlR13swo/58+4kItawj8TZTRi5ruwGy1w3Mzqzzb2cuuZQ jn6W6xOvnz05RiZDq2HX+r5hnANmU5rtRKwvul22urcMgAgpt1nOR7KHGBp7P6xXakgG 5v2NO9k0rYndwkK1/FX7WesxIGyRmDah5fiATnAyEOyg2MhSGPPcSN6V0LG89PgnD1UZ Y2Bw== X-Gm-Message-State: AJcUukcFjgF/C4afyxXek/KQr8yhTINkAeOvoB4zHSvi3iT/f8nlBlE+ jL50/VCgMI3nVCqBD0xaEQLuMa8p9apxN9rr6+Y= X-Received: by 2002:a0c:f50c:: with SMTP id j12mr16647911qvm.149.1547840021534; Fri, 18 Jan 2019 11:33:41 -0800 (PST) MIME-Version: 1.0 References: <20190118161835.2259170-1-arnd@arndb.de> <20190118161835.2259170-30-arnd@arndb.de> In-Reply-To: From: Arnd Bergmann Date: Fri, 18 Jan 2019 20:33:25 +0100 Message-ID: Subject: Re: [PATCH v2 29/29] y2038: add 64-bit time_t syscalls to all 32-bit architectures To: Andy Lutomirski Cc: y2038 Mailman List , Linux API , LKML , linux-arch , Matt Turner , Russell King , Catalin Marinas , Will Deacon , Tony Luck , Fenghua Yu , Geert Uytterhoeven , Michal Simek , Paul Burton , Helge Deller , Benjamin Herrenschmidt , Michael Ellerman , Martin Schwidefsky , Heiko Carstens , Rich Felker , "David S. Miller" , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , X86 ML , Max Filippov , Andrew Morton , Deepa Dinamani , "Eric W. Biederman" , Firoz Khan , alpha , linux-arm-kernel , linux-ia64@vger.kernel.org, linux-m68k , linux-mips@vger.kernel.org, Parisc List , linuxppc-dev , linux-s390 , Linux-sh list , sparclinux , Network Development , Linux FS Devel Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 18, 2019 at 7:50 PM Andy Lutomirski wrote: > On Fri, Jan 18, 2019 at 8:25 AM Arnd Bergmann wrote: > > - Once we get to 512, we clash with the x32 numbers (unless > > we remove x32 support first), and probably have to skip > > a few more. I also considered using the 512..547 space > > for 32-bit-only calls (which never clash with x32), but > > that also seems to add a bit of complexity. > > I have a patch that I'll send soon to make x32 use its own table. As > far as I'm concerned, 547 is *it*. 548 is just a normal number and is > not special. But let's please not reuse 512..547 for other purposes > on x86 variants -- that way lies even more confusion, IMO. Fair enough, the space for those numbers is cheap enough here. I take it you mean we also should not reuse that number space if we were to decide to remove x32 soon, but you are not worried about clashing with arch/alpha when everything else uses consistent numbers? Arnd