From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756669AbdKNUvu convert rfc822-to-8bit (ORCPT ); Tue, 14 Nov 2017 15:51:50 -0500 Received: from mail.efficios.com ([167.114.142.141]:57796 "EHLO mail.efficios.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752528AbdKNUvk (ORCPT ); Tue, 14 Nov 2017 15:51:40 -0500 Date: Tue, 14 Nov 2017 20:52:23 +0000 (UTC) From: Mathieu Desnoyers To: Ben Maurer Cc: Peter Zijlstra , "Paul E. McKenney" , Boqun Feng , Andy Lutomirski , Dave Watson , linux-kernel , linux-api , Paul Turner , Andrew Morton , Russell King , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Andrew Hunter , Andi Kleen , Chris Lameter , rostedt , Josh Triplett , Linus Torvalds , Catalin Marinas , Will Deacon , Michael Kerrisk , Alexander Viro Message-ID: <574606484.15158.1510692743725.JavaMail.zimbra@efficios.com> In-Reply-To: References: <20171114200414.2188-1-mathieu.desnoyers@efficios.com> <20171114200414.2188-2-mathieu.desnoyers@efficios.com> Subject: Re: [RFC PATCH v11 for 4.15 01/24] Restartable sequences system call MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT X-Originating-IP: [167.114.142.141] X-Mailer: Zimbra 8.7.11_GA_1854 (ZimbraWebClient - FF52 (Linux)/8.7.11_GA_1854) Thread-Topic: Restartable sequences system call Thread-Index: AQHTXYPhmIqd6HY5PUe1T5SV8sIkp6MUVZrNj4p9WjA= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org ----- On Nov 14, 2017, at 3:39 PM, Ben Maurer bmaurer@fb.com wrote: >>       int rseq(struct rseq * rseq, uint32_t rseq_len, int flags, uint32_t sig); > > Really dumb question -- and one I'm sorry to bring up at the last minute. Should > we consider making the syscall name something more generic "register_tls_abi"? > I'm assuming that if we ever want to use a per-thread userspace/kernel ABI > we'll want to use this field given the difficulty of getting adoption of > registration, the need to involve glibc, etc. It seems like there could be > future use cases of this TLS area that have nothing to do with rseq. I proposed that approach back in 2016 ("tls abi" system call), and the feedback I received back then is that it was preferred to have a dedicated "rseq" system call than an "open ended" and generic "tls abi" system call. Thanks, Mathieu -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com