From: Florian Weimer <fw@deneb.enyo.de>
To: Mathieu Desnoyers <mathieu.desnoyers@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: Thu, 18 May 2023 20:06:44 +0200 [thread overview]
Message-ID: <87o7mhms3v.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <e7dc7199-0b19-94ed-c764-12c07a447bb6@efficios.com> (Mathieu Desnoyers's message of "Thu, 18 May 2023 13:48:18 -0400")
* 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.
next prev parent reply other threads:[~2023-05-18 18:06 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 [this message]
2023-11-01 14:45 ` 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=87o7mhms3v.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=mathieu.desnoyers@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).