From: "H.J. Lu" <hjl.tools@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v2] x86-64: Allocate state buffer space for RDI, RSI and RBX
Date: Sun, 17 Mar 2024 05:57:16 -0700 [thread overview]
Message-ID: <CAMe9rOqybE4tRQQTZQBUj1PRn0m0AQjon948sz+7Ump9xQxfVw@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOqX_zAv3g6epjA7yGOojCKLZS+at+wtLWgXvwCvSi7wSQ@mail.gmail.com>
On Sun, Mar 17, 2024 at 4:39 AM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Sun, Mar 17, 2024 at 1:26 AM Florian Weimer <fweimer@redhat.com> wrote:
> >
> > * H. J. Lu:
> >
> > > diff --git a/sysdeps/x86/sysdep.h b/sysdeps/x86/sysdep.h
> > > index db8e576e91..262d4083e2 100644
> > > --- a/sysdeps/x86/sysdep.h
> > > +++ b/sysdeps/x86/sysdep.h
> > > @@ -46,6 +46,13 @@
> > > red-zone into account. */
> > > # define STATE_SAVE_OFFSET (8 * 7 + 8)
> > >
> > > +/* _dl_tlsdesc_dynamic preserves RDI, RSI and RBX before realigning
> > > + stack. After realigning stack, it saves RCX, RDX, R8, R9, R10 and
> > > + R11. Allocate space for all integer registers and round up the state
> > > + size to 64 bytes to avoid clobbering saved RDI, RSI and RBX values on
> > > + stack by xsave on STATE_SAVE_OFFSET(%rsp). */
> > > +# define TLSDESC_CALL_STATE_SAVE_OFFSET (STATE_SAVE_OFFSET + 64)
> >
> > Why 64? The red zone is 128 bytes, and the three registers only need 24
> > bytes. I think 24 has to be rounded up to 64 to preserve the XSAVE area
> > alignment.
>
> I changed it to 24.
>
> > The macro is also misnamed because it is not an offset. The real offset
> > depends on what the stack realignment did.
> >
>
> I renamed it to TLSDESC_CALL_REGISTER_SAVE_AREA in the v3 patch:
>
> https://patchwork.sourceware.org/project/glibc/list/?series=31971
>
No need to add a new test. Only sysdeps/x86_64/tst-gnu2-tls2mod1.S
is need:
https://patchwork.sourceware.org/project/glibc/list/?series=31975
--
H.J.
prev parent reply other threads:[~2024-03-17 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 3:13 H.J. Lu
2024-03-17 8:26 ` Florian Weimer
2024-03-17 11:39 ` H.J. Lu
2024-03-17 12:57 ` H.J. Lu [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=CAMe9rOqybE4tRQQTZQBUj1PRn0m0AQjon948sz+7Ump9xQxfVw@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=fweimer@redhat.com \
--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).