From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: "carlos@redhat.com" <carlos@redhat.com>,
Florian Weimer <fw@deneb.enyo.de>,
libc-alpha <libc-alpha@sourceware.org>
Subject: GNU libc support for extensible rseq ABI
Date: Thu, 18 May 2023 13:48:18 -0400 [thread overview]
Message-ID: <e7dc7199-0b19-94ed-c764-12c07a447bb6@efficios.com> (raw)
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 ?
You can find the librseq code supporting the extensible rseq ABI here:
https://git.kernel.org/pub/scm/libs/librseq/librseq.git/
specifically under src/rseq.c.
Thanks!
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next reply other threads:[~2023-05-18 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 17:48 Mathieu Desnoyers [this message]
2023-05-18 18:06 ` Florian Weimer
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=e7dc7199-0b19-94ed-c764-12c07a447bb6@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=carlos@redhat.com \
--cc=fw@deneb.enyo.de \
--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).