mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jürgen Groß" <jgross@suse.com>
To: Nathan Chancellor <nathan@kernel.org>, x86@kernel.org
Cc: linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
	kernel test robot <lkp@intel.com>,
	Sean Christopherson <seanjc@google.com>,
	Linux Kernel Functional Testing <lkft@linaro.org>
Subject: Re: [PATCH] x86/asm: Always inline serialize()
Date: Thu, 16 Jan 2025 15:32:10 +0100	[thread overview]
Message-ID: <14145470-070f-4249-8d6b-1a35a1b3ef21@suse.com> (raw)
In-Reply-To: <20250116-always-inline-serialize-for-noinstr-v1-1-b7a37b2af04b@kernel.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 1936 bytes --]

On 16.01.25 15:28, Nathan Chancellor wrote:
> serialize() may be called from noinstr code and if it is not inlined,
> objtool may warn like:
> 
>    vmlinux.o: warning: objtool: __static_call_update_early+0x2a: call to serialize() leaves .noinstr.text section
> 
> Mark serialize() with __always_inline to clear up the warning and
> prevent future ones from occurring.
> 
> Fixes: 0ef8047b737d ("x86/static-call: provide a way to do very early static-call updates")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/202412181756.aJvzih2K-lkp@intel.com/
> Reported-by: Sean Christopherson <seanjc@google.com>
> Closes: https://lore.kernel.org/Z4bWnWYqu1LaD-JG@google.com/
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> Closes: https://lore.kernel.org/CA+G9fYv-AgeUpP1yPDmy48T869Ms80jgUdjnwtBNoJmCKQvZDQ@mail.gmail.com/
> Signed-off-by: Nathan Chancellor <nathan@kernel.org>
> ---
>   arch/x86/include/asm/special_insns.h | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/x86/include/asm/special_insns.h b/arch/x86/include/asm/special_insns.h
> index fab7c8af27a4d00647f2f52e7fe4f91bd42a7291..03e7c2d495597597a635f83116fafa1a95ed357e 100644
> --- a/arch/x86/include/asm/special_insns.h
> +++ b/arch/x86/include/asm/special_insns.h
> @@ -211,7 +211,7 @@ static inline int write_user_shstk_64(u64 __user *addr, u64 val)
>   
>   #define nop() asm volatile ("nop")
>   
> -static inline void serialize(void)
> +static __always_inline void serialize(void)
>   {
>   	/* Instruction opcode for SERIALIZE; supported in binutils >= 2.35. */
>   	asm volatile(".byte 0xf, 0x1, 0xe8" ::: "memory");
> 
> ---
> base-commit: 37bc915c6ad0fb8a192dafb6b7046c79cad1f4a2
> change-id: 20250116-always-inline-serialize-for-noinstr-4e9e9826d967
> 
> Best regards,

I have sent the very same patch on Dec. 18th already.


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

      reply	other threads:[~2025-01-16 14:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16 14:28 Nathan Chancellor
2025-01-16 14:32 ` Jürgen Groß [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=14145470-070f-4249-8d6b-1a35a1b3ef21@suse.com \
    --to=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft@linaro.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=seanjc@google.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®