From: sashiko-bot@kernel.org
To: "Heiko Carstens" <hca@linux.ibm.com>
Cc: "Alexander Gordeev" <agordeev@linux.ibm.com>,
linux-s390@vger.kernel.org, "Heiko Carstens" <hca@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>
Subject: Re: [PATCH v3 05/11] s390/percpu/lowcore: Add and use LC_PERCPU lowcore offset defines
Date: Mon, 21 Sep 2026 08:45:57 +0000 [thread overview]
Message-ID: <20260921084558.1A5F91F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260921084005.4022574-6-hca@linux.ibm.com>
> Define LC_PERCPU_OFFSET and LC_PERCPU_REGISTER offset defines and use
> them in percpu code. This shortens the percpu inline assemblies and makes
> them a bit more readable.
>
> Note that because of header dependencies it is not possible to use
> asm-offsets. However to avoid adding more dependencies to asm-offsets
> it seems to be preferable to use the current approach in any way.
>
> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260921084005.4022574-1-hca@linux.ibm.com?part=5
next prev parent reply other threads:[~2026-09-21 8:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 8:39 [PATCH v3 00/11] s390: More this_cpu_*() changes Heiko Carstens
2026-09-21 8:39 ` [PATCH v3 01/11] s390/percpu: Fix comment typo Heiko Carstens
2026-09-21 8:41 ` sashiko-bot
2026-09-21 8:39 ` [PATCH v3 02/11] s390/percpu: Add sanity check to GEN_MVIY macro Heiko Carstens
2026-09-21 8:44 ` sashiko-bot
2026-09-21 8:39 ` [PATCH v3 03/11] s390/lowcore: Remove _AC() from LOWCORE_ALT_ADDRESS Heiko Carstens
2026-09-21 8:45 ` sashiko-bot
2026-09-21 8:39 ` [PATCH v3 04/11] s390/percpu: Let MVIY_PERCPU() calculate alternative displacement Heiko Carstens
2026-09-21 8:45 ` sashiko-bot
2026-09-21 8:39 ` [PATCH v3 05/11] s390/percpu/lowcore: Add and use LC_PERCPU lowcore offset defines Heiko Carstens
2026-09-21 8:45 ` sashiko-bot [this message]
2026-09-21 8:40 ` [PATCH v3 06/11] s390/percpu: Rename inline assembly symbolic names Heiko Carstens
2026-09-21 8:44 ` sashiko-bot
2026-09-21 8:40 ` [PATCH v3 07/11] s390/percpu: Use __PCPU_BEGIN() and __PCPU_END() for inline assemblies Heiko Carstens
2026-09-21 8:45 ` sashiko-bot
2026-09-21 8:40 ` [PATCH v3 08/11] s390/percpu: Use percpu code section for this_cpu_cmpxchg128() Heiko Carstens
2026-09-21 8:46 ` sashiko-bot
2026-09-21 8:40 ` [PATCH v3 09/11] s390/percpu: Use percpu code section for this_cpu_xchg() Heiko Carstens
2026-09-21 8:45 ` sashiko-bot
2026-09-21 8:40 ` [PATCH v3 10/11] s390/percpu: Use percpu code section for this_cpu_cmpxchg() Heiko Carstens
2026-09-21 8:52 ` sashiko-bot
2026-09-21 8:40 ` [PATCH v3 11/11] s390/percpu: Rework to simplify percpu_entry() and percpu_exit() Heiko Carstens
2026-09-21 8:52 ` sashiko-bot
2026-09-21 9:55 ` David Laight
2026-09-21 10:07 ` Mark Rutland
2026-09-21 10:17 ` Heiko Carstens
2026-09-21 9:15 ` [PATCH v3 00/11] s390: More this_cpu_*() changes Heiko Carstens
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=20260921084558.1A5F91F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.