From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: Restartable Sequences system call merged into Linux
Date: Wed, 11 Jul 2018 16:23:00 -0000 [thread overview]
Message-ID: <2c6c8f0e-4247-1649-8eaa-a885e4d51133@linaro.org> (raw)
In-Reply-To: <086b8e77-80e5-0908-0fdf-e4b19f087990@linux.ibm.com>
On 11/07/2018 13:03, Stefan Liebler wrote:
> On 06/11/2018 09:49 PM, Mathieu Desnoyers wrote:
>> Hi!
>>
>> Good news! The restartable sequences (rseq) system call is now merged into the master
>> branch of the Linux kernel within the 4.18 merge window:
>>
>> https://github.com/torvalds/linux/commit/d82991a8688ad128b46db1b42d5d84396487a508
>>
>> It would be important to discuss how we should proceed to integrate the library part
>> of rseq (see tools/testing/selftests/rseq/rseq*.{ch}) into glibc, or if it should
>> live in a standalone project.
>>
>> It should be noted that there can be only one rseq TLS area registered per thread,
>> which can then be used by many libraries and by the executable, so this is a
>> process-wide (per-thread) resource that we need to manage carefully.
>>
>> Thoughts ?
>>
>> Thanks!
>>
>> Mathieu
>>
>>
> The structs rseq_cs and rseq are aligned to 32 bytes.
> Please have a look at the bug:
> "Bug 23403 - Wrong alignment of TLS variables"
> (https://sourceware.org/bugzilla/show_bug.cgi?id=23403).
>
> @Carlos or somebody else:
> Should this be fixed in the upcoming glibc release?
I would consider this a block in fact.
next prev parent reply other threads:[~2018-07-11 16:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 19:49 Mathieu Desnoyers
2018-06-11 19:55 ` Florian Weimer
2018-06-11 20:04 ` Mathieu Desnoyers
2018-06-12 13:11 ` Florian Weimer
2018-06-12 16:31 ` Mathieu Desnoyers
2018-06-13 8:23 ` Florian Weimer
2018-06-14 12:28 ` Pavel Machek
2018-06-14 13:02 ` Mathieu Desnoyers
2018-06-14 13:26 ` Pavel Machek
2018-06-14 13:32 ` Florian Weimer
2018-06-14 13:46 ` Mathieu Desnoyers
2018-06-15 5:10 ` Florian Weimer
2018-06-15 17:44 ` Mathieu Desnoyers
2018-06-14 13:38 ` Mathieu Desnoyers
2018-06-14 13:50 ` Pavel Machek
2018-06-14 14:01 ` Florian Weimer
2018-06-14 14:36 ` Mathieu Desnoyers
2018-06-14 14:41 ` Florian Weimer
2018-06-14 15:09 ` Mathieu Desnoyers
2018-06-15 5:09 ` Florian Weimer
2018-06-15 17:50 ` Mathieu Desnoyers
2018-06-15 5:07 ` Florian Weimer
2018-06-13 11:48 ` Heiko Carstens
2018-06-13 16:14 ` Mathieu Desnoyers
2018-06-13 19:53 ` Mathieu Desnoyers
2018-07-11 16:03 ` Stefan Liebler
2018-07-11 16:23 ` Adhemerval Zanella [this message]
2018-07-11 17:19 ` Florian Weimer
2018-07-11 17:42 ` Adhemerval Zanella
2018-07-11 17:45 ` Florian Weimer
2018-07-11 17:59 ` Adhemerval Zanella
2018-07-12 8:08 ` Stefan Liebler
2018-07-11 19:05 ` Carlos O'Donell
2018-07-12 8:10 ` Szabolcs Nagy
2018-07-13 13:22 ` Stefan Liebler
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=2c6c8f0e-4247-1649-8eaa-a885e4d51133@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
/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).