From: DJ Delorie <dj@redhat.com>
To: Michael Jeanson <mjeanson@efficios.com>
Cc: libc-alpha@sourceware.org, mjeanson@efficios.com
Subject: Re: [PATCH v8 4/8] nptl: Add features to internal 'struct rseq_area'
Date: Fri, 16 Feb 2024 21:04:54 -0500 [thread overview]
Message-ID: <xnplwvg81l.fsf@greed.delorie.com> (raw)
In-Reply-To: <20240206162801.882585-5-mjeanson@efficios.com>
Michael Jeanson <mjeanson@efficios.com> writes:
> Access to features following the original rseq ABI 20 bytes (after
> 'flags') starting with 'node_id' must be gated by an rseq feature size
> test.
Are there any kernels that still provide auxvals that result in a 8 byte
rseq area? I.e. perhaps an older kernel that doesn't support the
feature area at all?
> diff --git a/sysdeps/unix/sysv/linux/rseq-internal.h b/sysdeps/unix/sysv/linux/rseq-internal.h
> index b6c9deea6b..a63e4afbdb 100644
> --- a/sysdeps/unix/sysv/linux/rseq-internal.h
> +++ b/sysdeps/unix/sysv/linux/rseq-internal.h
> @@ -28,13 +28,17 @@
> #include <ldsodefs.h>
>
> /* rseq area registered with the kernel. Use a custom definition
> - here to isolate from kernel struct rseq changes. The
> - implementation of sched_getcpu needs acccess to the cpu_id field;
> - the other fields are unused and not included here. */
> + here to isolate from kernel struct rseq changes. Access to fields
> + beyond the 20 bytes of the original ABI (after 'flags') must be gated
> + by a check of the feature size. */
If the answer to the first question is "yes" then this should be changed
to say "8 bytes" etc.
> struct rseq_area
> {
> uint32_t cpu_id_start;
> uint32_t cpu_id;
> + uint64_t rseq_cs;
> + uint32_t flags;
> + uint32_t node_id;
> + uint32_t mm_cid;
> };
Ok.
next prev parent reply other threads:[~2024-02-17 2:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 16:27 [PATCH v8 0/8] Extend rseq support Michael Jeanson
2024-02-06 16:27 ` [PATCH v8 1/8] nptl: fix potential merge of __rseq_* relro symbols Michael Jeanson
2024-02-06 16:41 ` Mathieu Desnoyers
2024-02-16 2:02 ` DJ Delorie
2024-02-16 20:18 ` Michael Jeanson
2024-02-16 20:29 ` DJ Delorie
2024-02-06 16:27 ` [PATCH v8 2/8] Add rseq extensible ABI support Michael Jeanson
2024-02-16 4:42 ` DJ Delorie
2024-02-16 20:19 ` Michael Jeanson
2024-02-16 20:37 ` DJ Delorie
2024-02-16 21:10 ` Michael Jeanson
2024-02-16 21:17 ` DJ Delorie
2024-02-16 21:24 ` Michael Jeanson
2024-02-06 16:27 ` [PATCH v8 3/8] nptl: Add public __rseq_feature_size symbol Michael Jeanson
2024-02-16 22:07 ` DJ Delorie
2024-02-19 19:25 ` Michael Jeanson
2024-02-19 19:43 ` DJ Delorie
2024-02-19 20:15 ` Michael Jeanson
2024-02-19 20:24 ` DJ Delorie
2024-02-19 22:06 ` Michael Jeanson
2024-02-19 22:08 ` DJ Delorie
2024-02-19 22:18 ` Michael Jeanson
2024-02-19 22:21 ` DJ Delorie
2024-02-06 16:27 ` [PATCH v8 4/8] nptl: Add features to internal 'struct rseq_area' Michael Jeanson
2024-02-17 2:04 ` DJ Delorie [this message]
2024-02-06 16:27 ` [PATCH v8 5/8] nptl: Add rseq internal utils Michael Jeanson
2024-02-17 2:33 ` DJ Delorie
2024-02-19 20:25 ` Michael Jeanson
2024-02-06 16:27 ` [PATCH v8 6/8] x86-64: Add rseq_load32_load32_relaxed Michael Jeanson
2024-02-17 3:08 ` DJ Delorie
2024-02-19 20:27 ` Michael Jeanson
2024-02-06 16:28 ` [PATCH v8 7/8] aarch64: " Michael Jeanson
2024-02-17 3:53 ` DJ Delorie
2024-02-19 20:29 ` Michael Jeanson
2024-02-20 15:07 ` Mathieu Desnoyers
2024-02-20 17:55 ` DJ Delorie
2024-02-06 16:28 ` [PATCH v8 8/8] Linux: Use rseq to accelerate getcpu Michael Jeanson
2024-02-17 3:57 ` DJ Delorie
2024-02-19 22:14 ` Michael Jeanson
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=xnplwvg81l.fsf@greed.delorie.com \
--to=dj@redhat.com \
--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).