public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Juergen Gross <jgross@suse.com>,
	Stefano Stabellini <sstabellini@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
	Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [PATCH v2] compiler: remove __ADDRESSABLE_ASM{_STR,}() again
Date: Fri, 14 Mar 2025 08:56:45 +0100	[thread overview]
Message-ID: <d66254fc-79a3-45cf-8195-ea0b49bb28a0@suse.com> (raw)
In-Reply-To: <20250217202943.p57k76tpwpx7aw6q@jpoimboe>

On 17.02.2025 21:29, Josh Poimboeuf wrote:
> On Mon, Feb 17, 2025 at 05:40:09PM +0100, Jan Beulich wrote:
>> __ADDRESSABLE_ASM_STR() is where the necessary stringification happens.
>> As long as "sym" doesn't contain any odd characters, no quoting is
>> required for its use with .quad / .long. In fact the quotation gets in
>> the way with gas 2.25; it's only from 2.26 onwards that quoted symbols
>> are half-way properly supported.
>>
>> However, assembly being different from C anyway, drop
>> __ADDRESSABLE_ASM_STR() and its helper macro altogether. A simple
>> .global directive will suffice to get the symbol "declared", i.e. into
>> the symbol table. While there also stop open-coding STATIC_CALL_TRAMP()
>> and STATIC_CALL_KEY().
>>
>> Fixes: 0ef8047b737d ("x86/static-call: provide a way to do very early static-call updates")
>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>> Cc: stable@vger.kernel.org
>> ---
>> v2: Drop constructs instead of fixing them. Use STATIC_CALL_KEY().
>> ---
>> Whether the "ADDRESSABLE" in __ADDRESSABLE_xen_hypercall is still
>> meaningful to keep I'm uncertain about. The situation, as said, is quite
>> different in assembly, compared to C's requirements.
> 
> The .global still makes it "addressable", so IMO it's named
> appropriately.
> 
> Thanks!
> 
> Acked-by: Josh Poimboeuf <jpoimboe@kernel.org>

Since this is addressing a (mild) regression, I wonder if this could still
make 6.14?

Jan

      reply	other threads:[~2025-03-14  7:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 16:40 [PATCH v2] compiler: remove __ADDRESSABLE_ASM{_STR,}() again Jan Beulich
2025-02-17 20:29 ` Josh Poimboeuf
2025-03-14  7:56   ` Jan Beulich [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=d66254fc-79a3-45cf-8195-ea0b49bb28a0@suse.com \
    --to=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=peterz@infradead.org \
    --cc=sstabellini@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