From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
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>,
Michael Kerrisk <mtk.manpages@gmail.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, 18 Jun 2020 13:22:14 +0100 [thread overview]
Message-ID: <20200618122213.GQ4066@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2006112026090.18393@digraph.polyomino.org.uk>
The 06/11/2020 20:26, Joseph Myers wrote:
> On Thu, 11 Jun 2020, Mathieu Desnoyers wrote:
> > I managed to get a repository up and running for librseq, and have integrated
> > the rseq.2 man page with comments from Michael Kerrisk here:
> >
> > https://git.kernel.org/pub/scm/libs/librseq/librseq.git/tree/doc/man/rseq.2
> >
> > Is that a suitable URL ? Can we simply point to it from glibc's manual ?
>
> Yes, that seems something reasonable to link to.
is there work to make the usage of rseq critical
sections portable? (e.g. transactional memory
critical section has syntax in gcc, but that
doesn't require straight line code with
begin/end/abort labels in a particular layout.)
the macros and inline asm in rseq-*.h are not
too nice, but if they can completely hide the
non-portable bits then i guess that works.
next prev parent reply other threads:[~2020-06-18 12:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200527185130.5604-1-mathieu.desnoyers@efficios.com>
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
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 [this message]
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
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=20200618122213.GQ4066@arm.com \
--to=szabolcs.nagy@arm.com \
--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=libc-alpha@sourceware.org \
--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