From: Joseph Myers <joseph@codesourcery.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Rich Felker <dalias@libc.org>, <libc-alpha@sourceware.org>,
<linux-api@vger.kernel.org>, Boqun Feng <boqun.feng@gmail.com>,
Will Deacon <will.deacon@arm.com>, <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ben Maurer <bmaurer@fb.com>, Dave Watson <davejwatson@fb.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <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: Wed, 3 Jun 2020 17:22:47 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2006031718070.7179@digraph.polyomino.org.uk> (raw)
In-Reply-To: <87d06gxsla.fsf@oldenburg2.str.redhat.com>
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@codesourcery.com
next prev parent reply other threads:[~2020-06-03 17:22 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
2020-05-27 18:51 ` [PATCH glibc 1/3] glibc: Perform rseq registration at C startup and thread creation (v20) Mathieu Desnoyers
2020-06-03 12:05 ` Florian Weimer
2020-06-03 12:22 ` Mathieu Desnoyers
2020-06-03 12:31 ` Florian Weimer
2020-06-03 12:40 ` Mathieu Desnoyers
2020-06-03 17:22 ` Joseph Myers [this message]
2020-06-04 11:10 ` Mathieu Desnoyers
2020-06-04 17:46 ` Joseph Myers
2020-06-11 17:47 ` Mathieu Desnoyers
2020-06-11 20:26 ` Joseph Myers
2020-06-18 12:22 ` Szabolcs Nagy
2020-06-18 13:03 ` Mathieu Desnoyers
2020-06-22 15:33 ` Mathieu Desnoyers
2020-05-27 18:51 ` [PATCH glibc 2/3] Linux: Use rseq in sched_getcpu if available (v9) Mathieu Desnoyers
2020-05-27 18:51 ` [PATCH glibc 3/3] rseq registration tests (v11) Mathieu Desnoyers
2020-06-03 12:07 ` [PATCH glibc 0/3] Restartable Sequences enablement Florian Weimer
2020-06-03 12:27 ` Mathieu Desnoyers
2020-06-03 12:33 ` Florian Weimer
2020-06-03 13:40 ` Florian Weimer
2020-06-05 17:04 ` Mathieu Desnoyers
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.2006031718070.7179@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=bmaurer@fb.com \
--cc=boqun.feng@gmail.com \
--cc=dalias@libc.org \
--cc=davejwatson@fb.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.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).