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=-0.9 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham 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 34C3EC67839 for ; Wed, 12 Dec 2018 18:14:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id EEB632084E for ; Wed, 12 Dec 2018 18:14:22 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org EEB632084E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=codesourcery.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728211AbeLLSOW (ORCPT ); Wed, 12 Dec 2018 13:14:22 -0500 Received: from relay1.mentorg.com ([192.94.38.131]:63393 "EHLO relay1.mentorg.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727990AbeLLSOU (ORCPT ); Wed, 12 Dec 2018 13:14:20 -0500 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=svr-ies-mbx-01.mgc.mentorg.com) by relay1.mentorg.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-SHA384:256) id 1gX91I-0005kK-LV from joseph_myers@mentor.com ; Wed, 12 Dec 2018 10:14:04 -0800 Received: from digraph.polyomino.org.uk (137.202.0.90) by svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 12 Dec 2018 18:14:01 +0000 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.90_1) (envelope-from ) id 1gX91E-0007Ah-I4; Wed, 12 Dec 2018 18:14:00 +0000 Date: Wed, 12 Dec 2018 18:14:00 +0000 From: Joseph Myers X-X-Sender: jsm28@digraph.polyomino.org.uk To: Arnd Bergmann CC: , Andy Lutomirski , Linus Torvalds , the arch/x86 maintainers , Linux Kernel Mailing List , Linux API , "H. Peter Anvin" , Peter Zijlstra , Borislav Petkov , Florian Weimer , , "H.J. Lu" , Rich Felker , , Will Deacon , Catalin Marinas Subject: Re: Can we drop upstream Linux x32 support? In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Originating-IP: [137.202.0.90] X-ClientProxiedBy: SVR-IES-MBX-08.mgc.mentorg.com (139.181.222.8) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 12 Dec 2018, Arnd Bergmann wrote: > > MIPS had o32, n32, n64 since like forever. > > o32 and n32 are practically the same, the only difference on the > syscall ABI that I can see are the actual syscall numbers, and > the 'struct sigcontext' definition. And for syscalls that have 64-bit arguments, n32 generally passes those in a single register (like n64), not pairs of registers (like o32). But, yes, userspace structure layout for n32 is generally much closer to o32 than to n64. -- Joseph S. Myers joseph@codesourcery.com