From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752070AbbIKIr5 (ORCPT <rfc822;w@1wt.eu>);
	Fri, 11 Sep 2015 04:47:57 -0400
Received: from mout.kundenserver.de ([212.227.126.187]:56872 "EHLO
	mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751955AbbIKIry (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 11 Sep 2015 04:47:54 -0400
From: Arnd Bergmann <arnd@arndb.de>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
        Geert Uytterhoeven <geert@linux-m68k.org>,
        Andy Lutomirski <luto@kernel.org>, X86 ML <x86@kernel.org>,
        Network Development <netdev@vger.kernel.org>,
        Tulio Magno Quites Machado Filho 
	<tuliom@linux.vnet.ibm.com>,
        Andy Lutomirski <luto@amacapital.net>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Alexander Larsson <alexl@redhat.com>,
        Cosimo Cecchi <cosimo@endlessm.com>,
        Dan Nicholson <nicholson@endlessm.com>,
        libc-alpha <libc-alpha@sourceware.org>,
        Rajalakshmi Srinivasaraghavan <raji@linux.vnet.ibm.com>,
        Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] x86: Wire up 32-bit direct socket calls
Date: Fri, 11 Sep 2015 10:46:26 +0200
Message-ID: <49726621.LPTnfQXYGz@wuerfel>
User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; )
In-Reply-To: <20150911082429.GA12452@osiris>
References: <cb5138299d37d5800e2d135b01a7667fa6115854.1436912629.git.luto@kernel.org> <3193269.4TGcgnGPrm@wuerfel> <20150911082429.GA12452@osiris>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Provags-ID: V03:K0:TSR5CcQOPYbKtZKWqWApyIEaabW/RznYgduHKiFdRri3dwbhJnp
 MH3TVycG4N1YiRcerJCQiWSANdTL10LRDdOzpOkr37tULFi2W8KZzY2wayF0vwmagLlUC0m
 mIO2ZU0J5SWwodG7bPpOyEsZ0FdCWAuLpVRqGrqh6SdpiFGfB1fzUsfRvxs4Y5nwawcL2pP
 gH747ng2umGfTGUlN1lSQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:czJoiUSchPo=:7e38kzymY/APIfG1pEGmoA
 VLuoHK9L2JTWtowFAP27gIiv/FVq9EMXdvw6K1ZYr2pkrjtbEZmuedDNQjLjCoWGGcGwSM/3x
 VIIt2ZDf1OLLwBEKkyLVSQ2/S2YBtqxTjemBxiFNEqWiEdVb6rjxPW2suB0X7BumHj0JemKS4
 pwDRI1AWIb1pvsI53ClIcQOhrN6Eqkyg7BBjmlYhxTSFLvLRdnhfE8JLtVH4LOn0Z/QgIZVpm
 9OQTt4IKNr3NNU7PjgRD/19YpjxLY4CTVimM0Xds9rn2qpnMSGGAYANR6JaxSmjjSdFRxD8GG
 WqZxIi77Vly6nLLb0yj+t8BYlqLr6ptluPEp2jh38XETr7m8iN+IsSpLapvZt+hSThpO10WzF
 YAICP/0837XZIGUtz+eAsHDZb2M6f7JKYMm6/dKWBweKLbQ/CfTTJEGvlxN0udBgjQXwt/GWV
 U8KpC6AL/mY9BFoIGOVdMARowAQu7jIOD4O+6/PKb7avwW82XYSVqOgjaparVliOE2JAcr+xx
 BlQVhTvEfCASVurhWprt2iOXdeIcshOm0TPoHm/E/Jw7U5Gn01ptR8nGMKdYiLfTK/7sVrZ0c
 GnBtJATulp+3Rgq5GMld0+vy559p/xUouolXB28WEX9cIoxm3v+e9dblDi/jeQN7AmRK4df4e
 h97pjg+IoSJs1wKnGrDYytQHXBZMveF6U/LXsZxQfHLfoAh3l31Xvyqw271Ec0eb8kS5GyQWr
 LeUI51YBtiHBof3g
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Friday 11 September 2015 10:24:29 Heiko Carstens wrote:
> 
> FWIW, the s390 approach (ignoring the "new" system calls) is only temporarily.
> I'll enable the seperate calls later when I have time to test everything,
> especially the glibc stuff.

Ok, thanks for clarifying.

> The same is true for the ipc system call. (any reason why the seperate system
> calls haven't been enabled on x86 now as well?)

Agreed, we should split that out on all architectures as well.
Almost the same set of architectures that have sys_socketcall also
have sys_ipc, and the reasons for changing are identical. I don't
think we have any other system calls that are handled like this
on some architectures but not on others. There are a couple of
system calls (e.g. futex) that are also multiplexers, but at
least they do it consistently.

	Arnd