From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25547 invoked by alias); 11 Jun 2018 19:49:25 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 25517 invoked by uid 89); 11 Jun 2018 19:49:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.0 required=5.0 tests=BAYES_20,SPF_PASS autolearn=ham version=3.3.2 spammy=integrate, Hx-languages-length:802, H*UA:Zimbra, H*x:Zimbra X-HELO: mail.efficios.com DKIM-Filter: OpenDKIM Filter v2.10.3 mail.efficios.com EC9EE1BC5CC Date: Mon, 11 Jun 2018 19:49:00 -0000 From: Mathieu Desnoyers To: Carlos O'Donell , Florian Weimer Cc: Peter Zijlstra , "Paul E. McKenney" , Boqun Feng , Thomas Gleixner , linux-kernel , libc-alpha Message-ID: <1084280721.10859.1528746558696.JavaMail.zimbra@efficios.com> Subject: Restartable Sequences system call merged into Linux MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2018-06/txt/msg00209.txt.bz2 Hi! Good news! The restartable sequences (rseq) system call is now merged into the master branch of the Linux kernel within the 4.18 merge window: https://github.com/torvalds/linux/commit/d82991a8688ad128b46db1b42d5d84396487a508 It would be important to discuss how we should proceed to integrate the library part of rseq (see tools/testing/selftests/rseq/rseq*.{ch}) into glibc, or if it should live in a standalone project. It should be noted that there can be only one rseq TLS area registered per thread, which can then be used by many libraries and by the executable, so this is a process-wide (per-thread) resource that we need to manage carefully. Thoughts ? Thanks! Mathieu -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com