mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Uros Bizjak <ubizjak@gmail.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [PATCH -tip] x86/asm: Use %a instead of %c(%%rip) in rip_rel_ptr()
Date: Sun, 04 May 2025 23:09:15 -0700	[thread overview]
Message-ID: <79AB4DAE-18EE-4F3C-980F-46304C021EC1@zytor.com> (raw)
In-Reply-To: <CAMj1kXHLfa2OzT+mo8qFxp5NtLHxaxnO3+skt_we=QOTtPFUqw@mail.gmail.com>

On May 4, 2025 10:48:19 PM PDT, Ard Biesheuvel <ardb@kernel.org> wrote:
>On Mon, 5 May 2025 at 04:59, H. Peter Anvin <hpa@zytor.com> wrote:
>>
>> On 5/4/25 11:43, Uros Bizjak wrote:
>> > The "a" asm operand modifier substitutes a memory reference, with the
>> > actual operand treated as address.  For x86_64, when a symbol is
>> > provided, the "a" modifier emits "sym(%rip)" instead of "sym".
>> >
>
>Clang does not
>
>https://godbolt.org/z/5Y58T45f5
>
>> > No functional changes intended.
>> >
>
>NAK. There is a functional change with Clang, which does not emit
>%(rip), and this is the whole point of this thing.
>
>> > Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
>> > Cc: Thomas Gleixner <tglx@linutronix.de>
>> > Cc: Ingo Molnar <mingo@kernel.org>
>> > Cc: Borislav Petkov <bp@alien8.de>
>> > Cc: Dave Hansen <dave.hansen@linux.intel.com>
>> > Cc: "H. Peter Anvin" <hpa@zytor.com>
>> > Cc: Ard Biesheuvel <ardb@kernel.org>
>> > ---
>> >   arch/x86/include/asm/asm.h | 2 +-
>> >   1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/arch/x86/include/asm/asm.h b/arch/x86/include/asm/asm.h
>> > index f963848024a5..d7610b99b8d8 100644
>> > --- a/arch/x86/include/asm/asm.h
>> > +++ b/arch/x86/include/asm/asm.h
>> > @@ -116,7 +116,7 @@
>> >   #ifndef __ASSEMBLER__
>> >   static __always_inline __pure void *rip_rel_ptr(void *p)
>> >   {
>> > -     asm("leaq %c1(%%rip), %0" : "=r"(p) : "i"(p));
>> > +     asm("leaq %a1, %0" : "=r"(p) : "i"(p));
>> >
>> >       return p;
>> >   }
>>
>> Also, this function really should be __attribute_const__ rather than __pure.
>>
>
>No it should really not.
>
>rip_rel_ptr() will yield different results depending on whether it is
>called [by the same code] from the 1:1 mapping or the ordinary kernel
>virtual mapping of memory, and this is basically the entire reason we
>need it in the first place.
>
>Lying to the compiler about this is not a good idea imo.

Goddamnit, another clang bug. Someone fix the damned thing, please...

  reply	other threads:[~2025-05-05  6:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-04 18:43 Uros Bizjak
2025-05-05  2:55 ` H. Peter Anvin
2025-05-05  2:59 ` H. Peter Anvin
2025-05-05  5:48   ` Ard Biesheuvel
2025-05-05  6:09     ` H. Peter Anvin [this message]
2025-05-05 10:42       ` Ard Biesheuvel
2025-05-05 11:49         ` H. Peter Anvin
2025-05-05 12:01           ` Ard Biesheuvel
2025-05-05 12:40             ` H. Peter Anvin
2025-05-05  6:15     ` Uros Bizjak

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=79AB4DAE-18EE-4F3C-980F-46304C021EC1@zytor.com \
    --to=hpa@zytor.com \
    --cc=ardb@kernel.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=ubizjak@gmail.com \
    --cc=x86@kernel.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

all inboxes | Powered by JetHome®