From: Rich Felker <dalias@libc.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Carlos O'Donell <carlos@redhat.com>,
Florian Weimer <fweimer@redhat.com>,
Joseph Myers <joseph@codesourcery.com>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
libc-alpha@sourceware.org, Thomas Gleixner <tglx@linutronix.de>,
Ben Maurer <bmaurer@fb.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Boqun Feng <boqun.feng@gmail.com>,
Will Deacon <will.deacon@arm.com>,
Dave Watson <davejwatson@fb.com>, Paul Turner <pjt@google.com>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation
Date: Thu, 22 Nov 2018 09:36:03 -0500 [thread overview]
Message-ID: <20181122143603.GD23599@brightrain.aerifal.cx> (raw)
In-Reply-To: <20181121183936.8176-1-mathieu.desnoyers@efficios.com>
On Wed, Nov 21, 2018 at 01:39:32PM -0500, Mathieu Desnoyers wrote:
> Register rseq(2) TLS for each thread (including main), and unregister
> for each thread (excluding main). "rseq" stands for Restartable
> Sequences.
Maybe I'm missing something obvious, but "unregister" does not seem to
be a meaningful operation. Can you clarify what it's for?
Rich
next prev parent reply other threads:[~2018-11-22 14:36 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 18:39 [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation Mathieu Desnoyers
2018-11-21 18:39 ` [RFC PATCH v4 2/5] glibc: sched_getcpu(): use rseq cpu_id TLS on Linux Mathieu Desnoyers
2018-11-22 14:36 ` Rich Felker [this message]
2018-11-22 15:04 ` [RFC PATCH v4 1/5] glibc: Perform rseq(2) registration at nptl init and thread creation Mathieu Desnoyers
2018-11-22 15:11 ` Florian Weimer
2018-11-22 15:17 ` Rich Felker
2018-11-22 15:21 ` Florian Weimer
2018-11-22 15:33 ` Mathieu Desnoyers
2018-11-22 15:44 ` Rich Felker
2018-11-22 16:24 ` Szabolcs Nagy
2018-11-22 18:35 ` Mathieu Desnoyers
2018-11-22 19:01 ` Rich Felker
2018-11-22 19:36 ` Mathieu Desnoyers
2018-11-22 15:14 ` Rich Felker
2018-11-22 15:47 ` Mathieu Desnoyers
2018-11-22 16:28 ` Florian Weimer
2018-11-22 16:47 ` Mathieu Desnoyers
2018-11-22 16:59 ` Florian Weimer
2018-11-22 17:10 ` Rich Felker
2018-11-23 13:10 ` Florian Weimer
2018-11-23 14:28 ` Rich Felker
2018-11-23 17:05 ` Mathieu Desnoyers
2018-11-23 17:30 ` Rich Felker
2018-11-23 17:39 ` Florian Weimer
2018-11-23 17:44 ` Rich Felker
2018-11-23 18:01 ` Florian Weimer
2018-11-23 17:52 ` Mathieu Desnoyers
2018-11-23 18:35 ` Rich Felker
2018-11-23 21:09 ` Mathieu Desnoyers
2018-11-26 8:28 ` Florian Weimer
2018-11-26 15:51 ` Mathieu Desnoyers
2018-11-26 16:03 ` Florian Weimer
2018-11-26 17:10 ` Rich Felker
2018-11-26 19:22 ` Mathieu Desnoyers
2018-12-03 21:30 ` Mathieu Desnoyers
2018-11-26 16:30 ` Mathieu Desnoyers
2018-11-26 17:07 ` Rich Felker
2018-12-05 17:24 ` Mathieu Desnoyers
2018-11-26 11:56 ` Szabolcs Nagy
2018-11-22 17:29 ` Mathieu Desnoyers
2018-11-23 13:29 ` Florian Weimer
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=20181122143603.GD23599@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=bmaurer@fb.com \
--cc=boqun.feng@gmail.com \
--cc=carlos@redhat.com \
--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=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 NNTP newsgroup(s).