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 [thread overview]
Message-ID: <49726621.LPTnfQXYGz@wuerfel> (raw)
In-Reply-To: <20150911082429.GA12452@osiris>
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
next prev parent reply other threads:[~2015-09-11 8:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 22:24 [PATCH] x86: Wire up 32-bit direct socket calls Andy Lutomirski
2015-07-21 9:41 ` [tip:x86/asm] x86/entry/syscalls: " tip-bot for Andy Lutomirski
2015-09-02 9:48 ` [PATCH] x86: " Geert Uytterhoeven
2015-09-02 20:16 ` H. Peter Anvin
2015-09-03 10:06 ` David Laight
2015-09-03 10:06 ` David Laight
2015-09-07 12:53 ` Arnd Bergmann
2015-09-11 8:24 ` Heiko Carstens
2015-09-11 8:46 ` Arnd Bergmann [this message]
2015-09-11 9:54 ` Geert Uytterhoeven
2015-09-11 10:14 ` Arnd Bergmann
2015-09-11 16:32 ` Andy Lutomirski
2015-09-14 13:35 ` Ingo Molnar
2015-09-15 20:55 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49726621.LPTnfQXYGz@wuerfel \
--to=arnd@arndb.de \
--cc=alexl@redhat.com \
--cc=cosimo@endlessm.com \
--cc=geert@linux-m68k.org \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicholson@endlessm.com \
--cc=raji@linux.vnet.ibm.com \
--cc=tuliom@linux.vnet.ibm.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.