public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Michael Jeanson <mjeanson@efficios.com>
To: DJ Delorie <dj@redhat.com>
Cc: libc-alpha@sourceware.org, mathieu.desnoyers@efficios.com
Subject: Re: [PATCH v8 2/8] Add rseq extensible ABI support
Date: Fri, 16 Feb 2024 16:10:52 -0500	[thread overview]
Message-ID: <c341de20-3cbd-4efc-affb-2258c6bfc905@efficios.com> (raw)
In-Reply-To: <xn4je8gn79.fsf@greed.delorie.com>

On 2024-02-16 15 h 37, DJ Delorie wrote:
> Michael Jeanson <mjeanson@efficios.com> writes:
>>> The TLS doesn't get resized, does it?  Or am I thinking of the DTV?
>>
>> The terminology is a bit confusing and could be clarified, my
>> understanding is that the 'static TLS block' is the area where the 'TLS
>> blocks' from shared objects and the main executable are allocated and
>> the DTV is the array of descriptors that point to each of these 'TLS
>> blocks' inside the 'static TLS block'.
> 
> I might be thinking of where TLS data for dlopen()'d objects go, after
> the static TLS block is filled.
> 
>>> Isn't __rseq_size always at least 32 ?
>>
>> It's at least 32 when the registration succeeded, however if the
>> registration failed or was disabled by tunable then it's set to 0.
> 
> Are we sure?
> 
>    /* Default to the rseq ABI minimum sizes, this will reduce TLS usage to 32
>       bytes when rseq is disabled by tunables.  */
>    size_t rseq_size = TLS_DL_RSEQ_MIN_SIZE;
>    size_t rseq_align = TLS_DL_RSEQ_MIN_ALIGN;
>    bool do_rseq = true;
>    do_rseq = TUNABLE_GET_FULL (glibc, pthread, rseq, int, NULL);
>    if (do_rseq)
>      {
>        rseq_align = GLRO(dl_tls_rseq_align);
>        /* Make sure the rseq area size is at least the minimum ABI size and a
>           multiple of the requested aligment. */
>        rseq_size = roundup (MAX (GLRO(dl_tls_rseq_feature_size),
> 			      TLS_DL_RSEQ_MIN_SIZE), rseq_align);
>      }
> 
> 
> static inline bool
> rseq_register_current_thread (struct pthread *self, bool do_rseq)
> {
>    if (do_rseq)
>      {
>        /* The kernel expects 'rseq_area->rseq_cs == NULL' on registration, zero
>           the whole rseq area.  */
>        memset(rseq_get_area(), 0, GLRO (dl_tls_rseq_size));
>        int ret = INTERNAL_SYSCALL_CALL (rseq, rseq_get_area(),
>                                         GLRO (dl_tls_rseq_size),
>                                         0, RSEQ_SIG);
>        if (!INTERNAL_SYSCALL_ERROR_P (ret))
>          return true;
>      }
>    RSEQ_SETMEM (rseq_get_area(), cpu_id, RSEQ_CPU_ID_REGISTRATION_FAILED);
>    return false;
> }
When rseq registration is disabled by tunable we still need to allocate 
an rseq block because application code is allowed to check for the 
registration status by reading 'rseq->cpu_id'. So in this case we 
allocate the minimum ABI size of 32. Internally this is recorded in 
'dl_tls_rseq_size' but the application visible '_rseq_size' is left at 0 
(this happens in sysdeps/nptl/dl-tls_init_tp.c).

I'll try making this more clear with additional comments and finding a 
name for 'rseq_size' that is not so close to '__rseq_size'.


  reply	other threads:[~2024-02-16 21:10 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 [this message]
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
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=c341de20-3cbd-4efc-affb-2258c6bfc905@efficios.com \
    --to=mjeanson@efficios.com \
    --cc=dj@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).