Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Murzin <vladimir.murzin@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: peterz@infradead.org, catalin.marinas@arm.com, hca@linux.ibm.com,
	linux-kernel@vger.kernel.org, ruanjinjie@huawei.com,
	yang@os.amperecomputing.com, maz@kernel.org, will@kernel.org,
	ardb@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 06/13] arm64: percpu: Add infrastructure for preemptible this_cpu_*() ops
Date: Thu, 30 Jul 2026 13:04:36 +0100	[thread overview]
Message-ID: <53120347-2926-4d02-9e90-2c0c489b33bd@arm.com> (raw)
In-Reply-To: <amsudrskKg6uOUSf@J2N7QTR9R3.cambridge.arm.com>

On 7/30/26 11:59, Mark Rutland wrote:
> On Wed, Jul 29, 2026 at 03:25:52PM +0100, Vladimir Murzin wrote:
>> On 7/28/26 13:38, Mark Rutland wrote:
>>> +#define __VAL_PCPU_GPRS(pcp, off, addr)				\
>>> +	"("							\
>>> +		"(.L__gpr_num_" pcp  " << 0) | "		\
>>> +		"(.L__gpr_num_" off  " << 5) | "		\
>>> +		"(.L__gpr_num_" addr " << 10)"			\
>>> +	")"
>> Later in the patch, there is a comment stating that these registers
>> are not expected to overlap. I can also see that early-clobber
>> constraints are applied to the output registers later in the patch
>> series, so the code is correct.
>>
>> However, would it be possible to add assertions that detect register
>> overlap, perhaps something like:
>>
>> ".if (.L__gpr_num_" pcp "== .L__gpr_num_" off ") ||"	\
>> "    (.L__gpr_num_" pcp "== .L__gpr_num_" addr ") ||"	\
>> "    (.L__gpr_num_" off "== .L__gpr_num_" addr")"	\
>> ".error "inline asm registers overlap"			\
>> ".endif"						\
> That's a good idea. I've added the following:
> 
> | #define __ASSERT_PCPU_GPRS_UNIQUE(pcp, off, addr)                       \
> |         ".if ("                                                         \
> |                 "(.L__gpr_num_" pcp " == .L__gpr_num_" off ") || "      \
> |                 "(.L__gpr_num_" pcp " == .L__gpr_num_" addr ") || "     \
> |                 "(.L__gpr_num_" off " == .L__gpr_num_" addr")"          \
> |         "    )\n"                                                       \
> |         ".error \"PCPU GPRS overlap: {" pcp "," off "," addr "}\"\n"    \
> |         ".endif\n"
> | 
> | #define ____PCPU_GPRS_BEGIN(gprs, pcp, off, addr)                       \
> |         __DEFINE_ASM_GPR_NUMS                                           \
> |         __DEFINE_ASM_GPR_ALIASES                                        \
> |         __ASSERT_PCPU_GPRS_UNIQUE(pcp, off, addr)                       \
> |         "       mov w" off ", #" __VAL_PCPU_GPRS(pcp, off, addr) "\n"   \
> |         "       strh    w" off ", " gprs "\n"                           \
> |         __KERN_ASM_CPU_OFFSET(off) "\n"
> 
> With that, we have enough ".L__gpr_num_" string concatenation that we
> should probably have:
> 
> | #define __GPR_NUM(r)		"(.L__gpr_num_" r ")"
> 
> ... so I'll go add a preparatory patches adding that and cleaning up
> existing usage.
> 
> Mark.
> 

Awesome!

Cheers
Vladimir


  reply	other threads:[~2026-07-30 12:04 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28 12:38 [RFC PATCH 00/13] arm64: Preemptible this_cpu_*() operations Mark Rutland
2026-07-28 12:38 ` [RFC PATCH 01/13] arm64: preempt: Simplify and optimize __preempt_count_dec_and_test() Mark Rutland
2026-07-29  3:56   ` Jinjie Ruan
2026-07-28 12:38 ` [RFC PATCH 02/13] arm64: preempt: Treat should_resched() as unlikely Mark Rutland
2026-07-29  4:00   ` Jinjie Ruan
2026-07-28 12:38 ` [RFC PATCH 03/13] arm64: ptrace: Always inline pt_regs_[read,write}_reg() Mark Rutland
2026-07-29  4:02   ` Jinjie Ruan
2026-07-28 12:38 ` [RFC PATCH 04/13] arm64: percpu: Factor out percpu offset asm Mark Rutland
2026-07-29  4:03   ` Jinjie Ruan
2026-07-28 12:38 ` [RFC PATCH 05/13] arm64: gpr-num: Add wxN aliases for wN registers Mark Rutland
2026-07-28 12:38 ` [RFC PATCH 06/13] arm64: percpu: Add infrastructure for preemptible this_cpu_*() ops Mark Rutland
2026-07-28 14:19   ` Peter Zijlstra
2026-07-28 14:30     ` Peter Zijlstra
2026-07-28 16:03       ` Mark Rutland
2026-07-28 16:49         ` Peter Zijlstra
2026-07-28 15:53     ` Mark Rutland
2026-07-28 16:46       ` Peter Zijlstra
2026-07-28 16:49       ` Peter Zijlstra
2026-08-04 13:23         ` Mark Rutland
2026-07-28 16:51   ` Heiko Carstens
2026-07-29  8:16     ` Heiko Carstens
2026-07-29 14:25   ` Vladimir Murzin
2026-07-30 10:59     ` Mark Rutland
2026-07-30 12:04       ` Vladimir Murzin [this message]
2026-07-28 12:38 ` [RFC PATCH 07/13] arm64: percpu: Implement preemptible read/write ops Mark Rutland
2026-07-28 21:47   ` David Laight
2026-08-04 15:00     ` Mark Rutland
2026-07-28 22:05   ` David Laight
2026-08-04 15:05     ` Mark Rutland
2026-07-28 12:38 ` [RFC PATCH 08/13] arm64: percpu: Implement preemptible void RMW ops Mark Rutland
2026-07-28 12:38 ` [RFC PATCH 09/13] arm64: percpu: Implement preemptible return " Mark Rutland
2026-07-28 12:38 ` [RFC PATCH 10/13] arm64: percpu: Implement preemptible XCHG ops Mark Rutland
2026-07-28 12:38 ` [RFC PATCH 11/13] arm64: percpu: Implement preemptible CMPXCHG ops Mark Rutland
2026-07-28 12:38 ` [RFC PATCH 12/13] arm64: percpu: Implement preemptible CMPXCHG128 ops Mark Rutland
2026-07-28 12:38 ` [RFC PATCH 13/13] arm64: percpu: Remove _pcp_protect*() wrappers Mark Rutland

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=53120347-2926-4d02-9e90-2c0c489b33bd@arm.com \
    --to=vladimir.murzin@arm.com \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ruanjinjie@huawei.com \
    --cc=will@kernel.org \
    --cc=yang@os.amperecomputing.com \
    /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