Rust for Linux List
 help / color / mirror / Atom feed
From: "Gary Guo" <gary@garyguo.net>
To: "Jan Polensky" <japo@linux.ibm.com>, <hca@linux.ibm.com>,
	<gor@linux.ibm.com>, <agordeev@linux.ibm.com>, <ojeda@kernel.org>,
	<peterz@infradead.org>, <jpoimboe@kernel.org>,
	<jbaron@akamai.com>, <aliceryhl@google.com>
Cc: <borntraeger@linux.ibm.com>, <svens@linux.ibm.com>,
	<boqun@kernel.org>, <gary@garyguo.net>,
	<bjorn3_gh@protonmail.com>, <lossin@kernel.org>,
	<a.hindborg@kernel.org>, <tmgross@umich.edu>, <dakr@kernel.org>,
	<rostedt@goodmis.org>, <ardb@kernel.org>,
	<linux-s390@vger.kernel.org>, <rust-for-linux@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/4] s390/jump_label: Implement ARCH_STATIC_BRANCH_JUMP_ASM and ARCH_STATIC_BRANCH_ASM macros
Date: Tue, 12 May 2026 15:21:42 +0100	[thread overview]
Message-ID: <DIGRK1QK7G8H.1W24QCDZ3V1AC@garyguo.net> (raw)
In-Reply-To: <20260512105920.2426293-3-japo@linux.ibm.com>

On Tue May 12, 2026 at 11:59 AM BST, Jan Polensky wrote:
> Rust static branch support needs the s390 jump label instruction sequence
> and __jump_table emission in a reusable form. The current implementation
> embeds the sequence directly in the C asm goto blocks, which cannot be
> shared with Rust.
>
> Introduce ARCH_STATIC_BRANCH_ASM and ARCH_STATIC_BRANCH_JUMP_ASM to
> describe the brcl sequences for the likely-false and likely-true cases
> and to emit the same __jump_table entries as before. Switch the existing
> C helpers to use the new macros to avoid duplication without changing
> the generated code.
>
> Signed-off-by: Jan Polensky <japo@linux.ibm.com>
> ---
>  arch/s390/include/asm/jump_label.h | 33 +++++++++++++++++-------------
>  1 file changed, 19 insertions(+), 14 deletions(-)
>
> diff --git a/arch/s390/include/asm/jump_label.h b/arch/s390/include/asm/jump_label.h
> index d9cbc18f6b2e..1f0114150786 100644
> --- a/arch/s390/include/asm/jump_label.h
> +++ b/arch/s390/include/asm/jump_label.h
> @@ -23,15 +23,25 @@
>   * We use a brcl 0,<offset> instruction for jump labels so it
>   * can be easily distinguished from a hotpatch generated instruction.
>   */

The comment looks out of place now, you probably want to move
ARCH_JUMP_TABLE_ENTRY above it.

Best,
Gary

> +#define ARCH_JUMP_TABLE_ENTRY(key, label, local_label)	\
> +	".pushsection __jump_table,\"aw\"\n"		\
> +	".balign	8\n"				\
> +	".long	" local_label "-.," label "-.\n"	\
> +	".quad	" key "-.\n"				\
> +	".popsection\n"
> +
> +#define ARCH_STATIC_BRANCH_ASM(key, label)	\
> +	"0:	brcl 0," label "\n"		\
> +	ARCH_JUMP_TABLE_ENTRY(key, label, "0b")
> +
> +#define ARCH_STATIC_BRANCH_JUMP_ASM(key, label)	\
> +	"0:	brcl 15," label "\n"		\
> +	ARCH_JUMP_TABLE_ENTRY(key, label, "0b")
> +
>  static __always_inline bool arch_static_branch(struct static_key *key, bool branch)
>  {
> -	asm goto("0:	brcl 0,%l[label]\n"
> -			  ".pushsection __jump_table,\"aw\"\n"
> -			  ".balign	8\n"
> -			  ".long	0b-.,%l[label]-.\n"
> -			  ".quad	%0+%1-.\n"
> -			  ".popsection\n"
> -			  : : JUMP_LABEL_STATIC_KEY_CONSTRAINT (key), "i" (branch) : : label);
> +	asm goto(ARCH_STATIC_BRANCH_ASM("%0+%1", "%l[label]")
> +		: : JUMP_LABEL_STATIC_KEY_CONSTRAINT (key), "i" (branch) : : label);
>  	return false;
>  label:
>  	return true;
> @@ -39,13 +49,8 @@ static __always_inline bool arch_static_branch(struct static_key *key, bool bran
>  
>  static __always_inline bool arch_static_branch_jump(struct static_key *key, bool branch)
>  {
> -	asm goto("0:	brcl 15,%l[label]\n"
> -			  ".pushsection __jump_table,\"aw\"\n"
> -			  ".balign	8\n"
> -			  ".long	0b-.,%l[label]-.\n"
> -			  ".quad	%0+%1-.\n"
> -			  ".popsection\n"
> -			  : : JUMP_LABEL_STATIC_KEY_CONSTRAINT (key), "i" (branch) : : label);
> +	asm goto(ARCH_STATIC_BRANCH_JUMP_ASM("%0+%1", "%l[label]")
> +		: : JUMP_LABEL_STATIC_KEY_CONSTRAINT (key), "i" (branch) : : label);
>  	return false;
>  label:
>  	return true;


  reply	other threads:[~2026-05-12 14:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12 10:59 [PATCH 0/4] s390: enable Rust support and add required arch glue Jan Polensky
2026-05-12 10:59 ` [PATCH 1/4] s390/bug: Provide ARCH_WARN_ASM for Rust WARN/BUG support Jan Polensky
2026-05-12 10:59 ` [PATCH 2/4] s390/jump_label: Implement ARCH_STATIC_BRANCH_JUMP_ASM and ARCH_STATIC_BRANCH_ASM macros Jan Polensky
2026-05-12 14:21   ` Gary Guo [this message]
2026-05-12 10:59 ` [PATCH 3/4] rust/bindgen_parameters: Mark s390 types as opaque to prevent repr conflicts Jan Polensky
2026-05-12 14:23   ` Gary Guo
2026-05-12 10:59 ` [PATCH 4/4] s390: enable Rust support Jan Polensky
2026-05-12 12:10   ` Miguel Ojeda

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=DIGRK1QK7G8H.1W24QCDZ3V1AC@garyguo.net \
    --to=gary@garyguo.net \
    --cc=a.hindborg@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=aliceryhl@google.com \
    --cc=ardb@kernel.org \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=borntraeger@linux.ibm.com \
    --cc=dakr@kernel.org \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=japo@linux.ibm.com \
    --cc=jbaron@akamai.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=svens@linux.ibm.com \
    --cc=tmgross@umich.edu \
    /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