public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v4] x86_64: Update THREAD_SETMEM/THREAD_SETMEM_NC for IMM64
Date: Mon, 15 Mar 2021 23:01:36 -0400	[thread overview]
Message-ID: <cfb041fe-55c2-249d-9b94-19658fa5234e@redhat.com> (raw)
In-Reply-To: <CAMe9rOpTMDecZpBSmYPUfWRaXjxofVFB1NpFzFGpEP=Byfk_jQ@mail.gmail.com>

On 3/15/21 9:29 AM, H.J. Lu wrote:
> Here is the v4 patch.   OK for master?

Let me start from the beginning, just to clarify a few things for my review.

The original sequence was this:

  asm volatile ("movq %0,%%fs:%P1" :
		: IMM_MODE ((uint64_t) cast_to_integer (value)),
		  "i" (offsetof (struct pthread, member)));

With IMM_MODE being 'nr'/'ir' and allows:

i/n - immediate integer operand

r - register operand

You attempt to write a 64-bit constant to the TCB and the above code fails.

Does gcc attempt to encode a 64-bit immediate into %0 and the assembler fails?

What was the error?

Then we try to fix this with the new sequence:

  asm volatile ("movq %q0,%%fs:%P1" :
		: "i" ((uint64_t) cast_to_integer (value)),
		  "i" (offsetof (struct pthread, member)));

Note that "%q0" is a machine constraint for any register.

This enforces only "i" (immediate integer operand) but requires the compiler
pick a register with the machine constraint for "%q0", so you can have 64-bit
constants but the compiler must arrange (via more machine instructions
to get the constant in into a 64-bit register).

Your v4 follows:

> From d3854da28e1cfc2544226629b3b85ad6e2d6f4d4 Mon Sep 17 00:00:00 2001
> From: "H.J. Lu" <hjl.tools@gmail.com>
> Date: Fri, 8 Jan 2021 15:38:14 -0800
> Subject: [PATCH v4] x86_64: Update THREAD_SETMEM/THREAD_SETMEM_NC for IMM64
> 
> Since there is only "movq imm32s, mem64" and no "movq imm64, mem64", use
> "movq reg64, mem64" to store 64-bit constant> ---
>  sysdeps/x86_64/nptl/tls.h | 33 ++++++++++++++++++++++++++-------
>  1 file changed, 26 insertions(+), 7 deletions(-)
> 
> diff --git a/sysdeps/x86_64/nptl/tls.h b/sysdeps/x86_64/nptl/tls.h
> index 20f0958780..2a4739df64 100644
> --- a/sysdeps/x86_64/nptl/tls.h
> +++ b/sysdeps/x86_64/nptl/tls.h
> @@ -271,9 +271,18 @@ _Static_assert (offsetof (tcbhead_t, __glibc_unused2) == 0x80,
>  		       "i" (offsetof (struct pthread, member)));	      \
>       else /* 8 */							      \
>         {								      \
> -	 asm volatile ("movq %q0,%%fs:%P1" :				      \
> -		       : IMM_MODE ((uint64_t) cast_to_integer (value)),	      \
> -			 "i" (offsetof (struct pthread, member)));	      \
> +	 /* The value is constant and known to be <= 32-bit immediate value.  \
> +	    In this case we allow the compiler to optimize and use movq with  \
> +	    an immediate value.  */					      \
> +	 if (__builtin_constant_p (value)				      \
> +	     && (int64_t) (int32_t) (uintptr_t) value == (uintptr_t) value)   \

Note that I made a typo on my last review. My intent was to write this:

/* The value is constant and known to be <= 32-bit immediate value.  \
   In this case we allow the compiler to optimize and use movq with  \
   an immediate value.  */					      \
if (__builtin_constant_p (value)
    && (int64_t) (int32_t) (uintptr_t) value != (uintptr_t) value))
	   asm volatile ("movq %0,%%fs:%P1" :				      \
			 : IMM_MODE ((uint64_t) cast_to_integer (value)),     \
			   "i" (offsetof (struct pthread, member)));	      \
else
/* The value is not known and so we must assume it is at worst a 64-bit value.
   We can't optimize this and so we must use a register for the move. */
	   asm volatile ("movq %q0,%%fs:%P1" :				      \
			 : "i" ((uint64_t) cast_to_integer (value)),	      \
			   "i" (offsetof (struct pthread, member)));	      \

So in the case you write a 64-bit constant you get the else case.

But in the case you have normal known 32-bit values you get the movq with a imm32s.

Does that work?

Can you please verify that you get the first case for all the normal 32-bit constants?

Can you please verify that you get the second for the 64-bit constant write?


> +	   asm volatile ("movq %q0,%%fs:%P1" :				      \
> +			 : "i" ((uint64_t) cast_to_integer (value)),	      \
> +			   "i" (offsetof (struct pthread, member)));	      \
> +	 else								      \
> +	   asm volatile ("movq %0,%%fs:%P1" :				      \
> +			 : IMM_MODE ((uint64_t) cast_to_integer (value)),     \
> +			   "i" (offsetof (struct pthread, member)));	      \
>         }})
>  
>  
> @@ -296,10 +305,20 @@ _Static_assert (offsetof (tcbhead_t, __glibc_unused2) == 0x80,
>  		       "r" (idx));					      \
>       else /* 8 */							      \
>         {								      \
> -	 asm volatile ("movq %q0,%%fs:%P1(,%q2,8)" :			      \
> -		       : IMM_MODE ((uint64_t) cast_to_integer (value)),	      \
> -			 "i" (offsetof (struct pthread, member[0])),	      \
> -			 "r" (idx));					      \
> +	 /* The value is constant and known to be <= 32-bit immediate value.  \
> +	    In this case we allow the compiler to optimize and use movq with  \
> +	    an immediate value.  */					      \
> +	 if (__builtin_constant_p (value)				      \
> +	     && (int64_t) (int32_t) (uintptr_t) value == (uintptr_t) value)   \
> +	   asm volatile ("movq %q0,%%fs:%P1(,%q2,8)" :			      \
> +			 : "i" ((uint64_t) cast_to_integer (value)),	      \
> +			   "i" (offsetof (struct pthread, member[0])),	      \
> +			   "r" (idx));					      \
> +	 else								      \
> +	   asm volatile ("movq %0,%%fs:%P1(,%q2,8)" :			      \
> +			 : IMM_MODE ((uint64_t) cast_to_integer (value)),     \
> +			   "i" (offsetof (struct pthread, member[0])),	      \
> +			   "r" (idx));					      \
>         }})
>  
>  
> -- 
> 2.30.2
> 

-- 
Cheers,
Carlos.


  reply	other threads:[~2021-03-16  3:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02 19:12 [PATCH] " H.J. Lu
2021-03-01 13:30 ` Carlos O'Donell
2021-03-02 14:21   ` [PATCH v2] " H.J. Lu
2021-03-08 22:28     ` Carlos O'Donell
2021-03-09  0:09       ` [PATCH v3] " H.J. Lu
2021-03-15 12:49         ` Carlos O'Donell
2021-03-15 13:29           ` [PATCH v4] " H.J. Lu
2021-03-16  3:01             ` Carlos O'Donell [this message]
2021-03-16  9:04               ` Andreas Schwab
2021-03-16 15:45                 ` [PATCH v5] x86_64: Update THREAD_SETMEM/THREAD_SETMEM_NC for IMM64 [BZ #27591] H.J. Lu
2021-03-16 16:02                   ` Andreas Schwab
2021-03-16 16:10                     ` Florian Weimer
2021-03-16 16:34                       ` Carlos O'Donell
2021-03-16 16:50                         ` [PATCH v6] x86_64: Correct THREAD_SETMEM/THREAD_SETMEM_NC for movq " H.J. Lu
2021-03-16 16:52                           ` H.J. Lu

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=cfb041fe-55c2-249d-9b94-19658fa5234e@redhat.com \
    --to=carlos@redhat.com \
    --cc=hjl.tools@gmail.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).