From: Magnus Lindholm <linmag7@gmail.com>
To: richard.henderson@linaro.org, mattst88@gmail.com,
glaubitz@physik.fu-berlin.de, macro@orcam.me.uk,
macro@redhat.com, mcree@orcon.net.nz, ink@unseen.parts,
linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org
Cc: Magnus Lindholm <linmag7@gmail.com>
Subject: [PATCH 0/1] Add support for HAVE_ARCH_JUMP_LABEL
Date: Thu, 19 Feb 2026 17:58:31 +0100 [thread overview]
Message-ID: <20260219170013.15884-1-linmag7@gmail.com> (raw)
This patch adds jump label (static key) support for Alpha.
Testing and verification were performed on an UP2000+ system.
Verification steps:
- Confirmed __jump_table section is present at runtime via
/proc/kallsyms and contains a non-zero number of entries.
- Instrumented arch_jump_label_transform() to log patch
operations and verified instruction sites toggle between:
NOP (bis $31,$31,$31, 0x47ff041f)
BR (br $31,target)
- Added temporary instrumentation in
arch_jump_label_transform() to log old/new instruction
values at each patch site, and used a Python script to
validate correct NOP/BR transitions and branch encoding,
confirming functional runtime patching.
Instruction stream synchronization uses imb()/smp_imb() via
flush_icache_range(), and runtime behavior confirms correct
I-cache coherency.
The system remained stable throughout all testing.
Magnus Lindholm (1):
alpha: Add support for HAVE_ARCH_JUMP_LABEL
arch/alpha/Kconfig | 1 +
arch/alpha/include/asm/jump_label.h | 66 +++++++++++++++++++++++
arch/alpha/kernel/Makefile | 1 +
arch/alpha/kernel/jump_label.c | 81 +++++++++++++++++++++++++++++
4 files changed, 149 insertions(+)
create mode 100644 arch/alpha/include/asm/jump_label.h
create mode 100644 arch/alpha/kernel/jump_label.c
--
2.52.0
next reply other threads:[~2026-02-19 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 16:58 Magnus Lindholm [this message]
2026-02-19 16:58 ` [PATCH 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=20260219170013.15884-1-linmag7@gmail.com \
--to=linmag7@gmail.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=ink@unseen.parts \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=macro@redhat.com \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox