From: Mathieu Desnoyers via Libc-alpha <libc-alpha@sourceware.org>
To: Szabolcs Nagy <szabolcs.nagy@arm.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>,
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>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH glibc 1/3] glibc: Perform rseq registration at C startup and thread creation (v20)
Date: Thu, 18 Jun 2020 09:03:07 -0400 (EDT) [thread overview]
Message-ID: <906553413.6099.1592485387108.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <20200618122213.GQ4066@arm.com>
----- On Jun 18, 2020, at 8:22 AM, Szabolcs Nagy szabolcs.nagy@arm.com wrote:
> 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.
My goal with librseq is indeed to provide static inlines
which hide the architecture-specific ugliness of rseq
critical section assembly code behind an API which can be
used from all supported architectures for most of the
known use-cases, so only very specific use-case would
have to craft their own assembly.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2020-06-18 13:03 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
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 [this message]
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=906553413.6099.1592485387108.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=szabolcs.nagy@arm.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).