From: Mathieu Desnoyers via Libc-alpha <libc-alpha@sourceware.org>
To: Joseph Myers <joseph@codesourcery.com>,
Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
Rich Felker <dalias@libc.org>,
libc-alpha <libc-alpha@sourceware.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-api <linux-api@vger.kernel.org>,
Boqun Feng <boqun.feng@gmail.com>,
Will Deacon <will.deacon@arm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ben Maurer <bmaurer@fb.com>, Dave Watson <davejwatson@fb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Paul <paulmck@linux.vnet.ibm.com>, Paul Turner <pjt@google.com>
Subject: Re: [PATCH glibc 1/3] glibc: Perform rseq registration at C startup and thread creation (v20)
Date: Thu, 4 Jun 2020 07:10:56 -0400 (EDT) [thread overview]
Message-ID: <188671972.53608.1591269056445.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2006031718070.7179@digraph.polyomino.org.uk>
----- 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
next prev parent reply other threads:[~2020-06-04 11:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 18:51 [PATCH glibc 0/3] Restartable Sequences enablement Mathieu Desnoyers via Libc-alpha
2020-05-27 18:51 ` [PATCH glibc 1/3] glibc: Perform rseq registration at C startup and thread creation (v20) Mathieu Desnoyers via Libc-alpha
2020-06-03 12:05 ` Florian Weimer via Libc-alpha
2020-06-03 12:22 ` Mathieu Desnoyers via Libc-alpha
2020-06-03 12:31 ` Florian Weimer via Libc-alpha
2020-06-03 12:40 ` Mathieu Desnoyers via Libc-alpha
2020-06-03 17:22 ` Joseph Myers
2020-06-04 11:10 ` Mathieu Desnoyers via Libc-alpha [this message]
2020-06-04 17:46 ` Joseph Myers
2020-06-11 17:47 ` Mathieu Desnoyers via Libc-alpha
2020-06-11 20:26 ` Joseph Myers
2020-06-18 12:22 ` Szabolcs Nagy
2020-06-18 13:03 ` Mathieu Desnoyers via Libc-alpha
2020-06-22 15:33 ` Mathieu Desnoyers via Libc-alpha
2020-05-27 18:51 ` [PATCH glibc 2/3] Linux: Use rseq in sched_getcpu if available (v9) Mathieu Desnoyers via Libc-alpha
2020-05-27 18:51 ` [PATCH glibc 3/3] rseq registration tests (v11) Mathieu Desnoyers via Libc-alpha
2020-06-03 12:07 ` [PATCH glibc 0/3] Restartable Sequences enablement Florian Weimer via Libc-alpha
2020-06-03 12:27 ` Mathieu Desnoyers via Libc-alpha
2020-06-03 12:33 ` Florian Weimer via Libc-alpha
2020-06-03 13:40 ` Florian Weimer via Libc-alpha
2020-06-05 17:04 ` Mathieu Desnoyers via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=188671972.53608.1591269056445.JavaMail.zimbra@efficios.com \
--to=libc-alpha@sourceware.org \
--cc=bmaurer@fb.com \
--cc=boqun.feng@gmail.com \
--cc=dalias@libc.org \
--cc=davejwatson@fb.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mtk.manpages@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).