From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2B02FC433E0 for ; Thu, 4 Jun 2020 11:11:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 06470206A2 for ; Thu, 4 Jun 2020 11:11:03 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=efficios.com header.i=@efficios.com header.b="iYnI6N0d" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726026AbgFDLK6 (ORCPT ); Thu, 4 Jun 2020 07:10:58 -0400 Received: from mail.efficios.com ([167.114.26.124]:44980 "EHLO mail.efficios.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725882AbgFDLK6 (ORCPT ); Thu, 4 Jun 2020 07:10:58 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.efficios.com (Postfix) with ESMTP id EEBF32C5456; Thu, 4 Jun 2020 07:10:56 -0400 (EDT) Received: from mail.efficios.com ([127.0.0.1]) by localhost (mail03.efficios.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id lABorUU7fUUP; Thu, 4 Jun 2020 07:10:56 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.efficios.com (Postfix) with ESMTP id 952022C5455; Thu, 4 Jun 2020 07:10:56 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.efficios.com 952022C5455 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=efficios.com; s=default; t=1591269056; bh=1KUporPmaXnM01aB++UOwuHWfy+Lc+22xlsbm4M+iEY=; h=Date:From:To:Message-ID:MIME-Version; b=iYnI6N0dTWNo/PGXrBPIgA48+Bic32iPb5gH9BB+4odj9lFzDoNsDBYddXODI6OKT aPiIwzA8ajSDPSDYt7pVjJU9+h2Np+I43FJ2Up2C4HxpwUA1L5143hU1eyraoJn2J5 DSGIig7yN4OQa8MtafuSzE652+DV2C1l8R/JHiCMkxo7xszbnjCrrJzS44Xunz/D3t GBcE/CoS0bAhGvKU07FWiUKifyKIWg1DB70jQNtuVf9qqsBIuTRtLQsVtno64FHVl/ M1Ckp2a4yKev6d0W9FAKgZKo+0u7Vhr5KXtNPg2zsGTn4RNTgpAAOS58PoC2Gy9CmG NUhO7ZI8IMLzQ== X-Virus-Scanned: amavisd-new at efficios.com Received: from mail.efficios.com ([127.0.0.1]) by localhost (mail03.efficios.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id cI2TZ8maBAHa; Thu, 4 Jun 2020 07:10:56 -0400 (EDT) Received: from mail03.efficios.com (mail03.efficios.com [167.114.26.124]) by mail.efficios.com (Postfix) with ESMTP id 822AC2C553F; Thu, 4 Jun 2020 07:10:56 -0400 (EDT) Date: Thu, 4 Jun 2020 07:10:56 -0400 (EDT) From: Mathieu Desnoyers To: Joseph Myers , Michael Kerrisk Cc: Florian Weimer , Rich Felker , libc-alpha , linux-api , Boqun Feng , Will Deacon , linux-kernel , Peter Zijlstra , Ben Maurer , Dave Watson , Thomas Gleixner , Paul , Paul Turner Message-ID: <188671972.53608.1591269056445.JavaMail.zimbra@efficios.com> In-Reply-To: References: <20200527185130.5604-1-mathieu.desnoyers@efficios.com> <20200527185130.5604-2-mathieu.desnoyers@efficios.com> <87d06gxsla.fsf@oldenburg2.str.redhat.com> Subject: Re: [PATCH glibc 1/3] glibc: Perform rseq registration at C startup and thread creation (v20) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [167.114.26.124] X-Mailer: Zimbra 8.8.15_GA_3928 (ZimbraWebClient - FF76 (Linux)/8.8.15_GA_3928) Thread-Topic: glibc: Perform rseq registration at C startup and thread creation (v20) Thread-Index: zF49gywpspZcwIriHJ+0g73PGzbsCw== Sender: linux-api-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-api@vger.kernel.org ----- On Jun 3, 2020, at 1:22 PM, Joseph Myers joseph@codesourcery.com wrote: > On Wed, 3 Jun 2020, Florian Weimer via Libc-alpha wrote: > >> I'm still waiting for feedback from other maintainers whether the level >> of documentation and testing is appropriate. > > Looking at the documentation in the manual, it doesn't look like it has > enough information for someone to use this functionality, or to know when > they might want to use it, and nor does it point to external documentation > of it. It would seem appropriate at least to include a link to wherever > the external documentation is of what this functionality is good for, how > to create and use a "Restartable Sequence critical section", and how to > "perform rseq registration to the kernel". That external piece of documentation would be part of the Linux man-pages project, maintained by Michael Kerrisk. I have submitted a few revisions of the rseq(2) man page, but have been waiting for Michael to reply for more than a year now: https://lore.kernel.org/r/2021826204.69809.1588000508294.JavaMail.zimbra@efficios.com I'm thinking about hosting a rseq(2) man-page into my librseq project, would that make sense ? librseq is currently a development branch in my own repository for now. It still needs to be tweaked to adapt to the various changes that went into the glibc rseq enablement patchset, and then I plan to move it to a more "formal" home: https://github.com/compudj/librseq Thanks, Mathieu -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com