From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mathieu Desnoyers Subject: Re: [RFC PATCH v11 for 4.15 01/24] Restartable sequences system call Date: Tue, 14 Nov 2017 20:52:23 +0000 (UTC) Message-ID: <574606484.15158.1510692743725.JavaMail.zimbra@efficios.com> References: <20171114200414.2188-1-mathieu.desnoyers@efficios.com> <20171114200414.2188-2-mathieu.desnoyers@efficios.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org 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 List-Id: linux-api@vger.kernel.org ----- On Nov 14, 2017, at 3:39 PM, Ben Maurer bmaurer-b10kYP2dOMg@public.gmane.org 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