From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9BBEFC07EBF for ; Fri, 18 Jan 2019 19:36:11 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 13EE520657 for ; Fri, 18 Jan 2019 19:36:10 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 13EE520657 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=arndb.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 43hB5459ZZzDrBf for ; Sat, 19 Jan 2019 06:36:08 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=gmail.com (client-ip=209.85.160.193; helo=mail-qt1-f193.google.com; envelope-from=arndbergmann@gmail.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=arndb.de Received: from mail-qt1-f193.google.com (mail-qt1-f193.google.com [209.85.160.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 43hB2H5R49zDrCl for ; Sat, 19 Jan 2019 06:33:43 +1100 (AEDT) Received: by mail-qt1-f193.google.com with SMTP id l12so16459670qtf.8 for ; Fri, 18 Jan 2019 11:33:43 -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=Won9ezj8kN7+PpjlKwriVM1+nGiKYBN63IYOdAem+GuhPIIahEtDZl0jHRtWhgV6+W ymu5IOb1MO/UDjTEp5rhif64kJ965lmqn//0HLiTDllHCcKT8chTjxlGqafDNKIpOvor SIq/Cw8SXDrlLr2HiI6fANuhve5xrZhHGQqFuZ2/oxJo6/Ez4a6C5YI82LWgbFXZ6CPC A7Y5x8pqv2KhJZrf2O81DbRLX+WzvSUVYgCkqQdsqjEr+ubAdM7ZoIxF+xKSRK0jcQmU PrzMIHvgA43wn4lTNFHKyoRsMHaFA3kUj3ni9ycpvws8X3qq1rzAiycyc4eNHBIKGA4m ue2Q== X-Gm-Message-State: AJcUukfEK3L+peg2MuIPBCzoktZGl3ejoGipI9IsG7DJ2/gltb9PuNWN K94y1aEwJDAymCCrdru5820qufuG/s9TOoUOCfE= X-Google-Smtp-Source: ALg8bN51ZSz8S/UEkmKkQ76yrnTrRmtVHEOrjwWqzHKH/uRWMtRP1y/XgFacGAOrjnX1tIv/Wxgb87NR61MktkAeKK4= 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 Content-Type: text/plain; charset="UTF-8" X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Rich Felker , linux-ia64@vger.kernel.org, Linux-sh list , Heiko Carstens , linux-mips@vger.kernel.org, Max Filippov , Network Development , Deepa Dinamani , "H. Peter Anvin" , sparclinux , linux-arch , linux-s390 , y2038 Mailman List , Helge Deller , X86 ML , Russell King , Ingo Molnar , Geert Uytterhoeven , Catalin Marinas , Firoz Khan , Matt Turner , Fenghua Yu , Will Deacon , Linux FS Devel , linux-m68k , Thomas Gleixner , linux-arm-kernel , Michal Simek , Tony Luck , Parisc List , Linux API , LKML , Paul Burton , "Eric W. Biederman" , alpha , Martin Schwidefsky , Andrew Morton , linuxppc-dev , "David S. Miller" Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" 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