[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.2006031718070.7179@digraph.polyomino.org.uk>
Date: Wed, 3 Jun 2020 17:22:47 +0000
From: Joseph Myers <joseph@...esourcery.com>
To: Florian Weimer <fweimer@...hat.com>
CC: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Rich Felker <dalias@...c.org>, <libc-alpha@...rceware.org>,
<linux-api@...r.kernel.org>, Boqun Feng <boqun.feng@...il.com>,
Will Deacon <will.deacon@....com>,
<linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ben Maurer <bmaurer@...com>, Dave Watson <davejwatson@...com>,
Thomas Gleixner <tglx@...utronix.de>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Paul Turner <pjt@...gle.com>
Subject: Re: [PATCH glibc 1/3] glibc: Perform rseq registration at C startup
and thread creation (v20)
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".
--
Joseph S. Myers
joseph@...esourcery.com
Powered by blists - more mailing lists