From: Magnus Lindholm <linmag7@gmail.com>
To: richard.henderson@linaro.org, mattst88@gmail.com,
linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org
Cc: linmag7@gmail.com
Subject: [PATCH v4 0/1] alpha: Add support for HAVE_ARCH_JUMP_LABEL
Date: Sun, 15 Nov 2026 10:37:47 +0100 [thread overview]
Message-ID: <20261115093752.1287968-1-linmag7@gmail.com> (raw)
Apply-time cleanups following Matt Turner's review of v3:
- Move jump_label.o beside the other object entries near the top of
arch/alpha/kernel/Makefile, outside the GENERIC block.
- Include linux/cacheflush.h instead of asm/cacheflush.h.
- Regenerate the cover-letter diffstat and retain Matt's Reviewed-by.
The jump-label implementation is otherwise unchanged from v3.
V3 was cross-built with W=1 and boot-tested on a three-CPU AlphaServer
ES40 with CMA v2. The static-key boot selftest and 30 module load/unload
cycles passed, including cross-module keys. This revised export has
not been rebuilt or boot-tested separately.
Batching I-cache synchronization and relative jump-table entries remain
follow-ups. The early jump_label_init() call needed before Alpha's new
early-parameter parsing is carried by the separate CMA v3 series.
This patch applies to for-next at 0b4cadbe7c39.
Magnus Lindholm (1):
alpha: Add support for HAVE_ARCH_JUMP_LABEL
.../core/jump-labels/arch-support.txt | 2 +-
arch/alpha/Kconfig | 1 +
arch/alpha/include/asm/jump_label.h | 65 +++++++++++++++
arch/alpha/kernel/Makefile | 1 +
arch/alpha/kernel/jump_label.c | 79 +++++++++++++++++++
5 files changed, 147 insertions(+), 1 deletion(-)
create mode 100644 arch/alpha/include/asm/jump_label.h
create mode 100644 arch/alpha/kernel/jump_label.c
base-commit: 0b4cadbe7c39d830dec35c4a2655483de0dae568
--
2.43.0
next reply other threads:[~2026-11-15 9:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 9:37 Magnus Lindholm [this message]
2026-11-15 9:37 ` [PATCH v4 1/1] alpha: Add support for HAVE_ARCH_JUMP_LABEL Magnus Lindholm
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=20261115093752.1287968-1-linmag7@gmail.com \
--to=linmag7@gmail.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=richard.henderson@linaro.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 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.