From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Florian Weimer <fw@deneb.enyo.de>,
Michael Jeanson <mjeanson@efficios.com>
Cc: "carlos@redhat.com" <carlos@redhat.com>,
libc-alpha <libc-alpha@sourceware.org>
Subject: Re: GNU libc support for extensible rseq ABI
Date: Wed, 1 Nov 2023 10:45:29 -0400 [thread overview]
Message-ID: <1c5b9ef4-f241-4577-838e-37f0104a6a7c@efficios.com> (raw)
In-Reply-To: <87o7mhms3v.fsf@mid.deneb.enyo.de>
On 2023-05-18 14:06, Florian Weimer wrote:
> * Mathieu Desnoyers:
>
>> Hi Carlos, Florian,
>>
>> Now that the 6.3 Linux kernel is out, the ABI for extensible rseq is
>> frozen, and we could add support for it in glibc. It would be good to
>> upstream this support before we run out of room in the padding space we
>> currently re-use.
>>
>> What glibc release should we target for this ?
>
> It may be possible to hack this into the existing TLS allocator. See
> the loop in _dl_determine_tlsoffset. It should be possible to add the
> rseq area as another static TLS block (perhaps as the first one before
> the loop), with the size and alignment requested by the kernel. If we
> can make that work, it's going to be a fairly small patch that should
> be backportable as well. That could go into 2.38 or 2.39.
>
> If we need a new TLS allocator, it's definitely 2.39 material at this
> point, potentially later.
Michael (in CC) showed interest in working on this. I'm adding him to
this e-mail thread so you are both aware of each other's ongoing progress.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
prev parent reply other threads:[~2023-11-01 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 17:48 Mathieu Desnoyers
2023-05-18 18:06 ` Florian Weimer
2023-11-01 14:45 ` Mathieu Desnoyers [this message]
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=1c5b9ef4-f241-4577-838e-37f0104a6a7c@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=carlos@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.org \
--cc=mjeanson@efficios.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).