From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org, Marc Zyngier <maz@kernel.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
Mostafa Saleh <smostafa@google.com>,
Mark Rutland <mark.rutland@arm.com>,
Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH] arm64: Unconditionally select CONFIG_JUMP_LABEL
Date: Fri, 4 Jul 2025 18:44:16 +0100 [thread overview]
Message-ID: <175163687202.1322627.833974757174570861.b4-ty@kernel.org> (raw)
In-Reply-To: <20250613141936.2219895-1-maz@kernel.org>
On Fri, 13 Jun 2025 15:19:36 +0100, Marc Zyngier wrote:
> Aneesh reports that his kernel fails to boot in nVHE mode with
> KVM's protected mode enabled. Further investigation by Mostafa
> reveals that this fails because CONFIG_JUMP_LABEL=n and that
> we have static keys shared between EL1 and EL2.
>
> While this can be worked around, it is obvious that we have long
> relied on having CONFIG_JUMP_LABEL enabled at all times, as all
> supported compilers now have 'asm goto' (which is the basic block
> for jump labels).
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: Unconditionally select CONFIG_JUMP_LABEL
https://git.kernel.org/arm64/c/727c2a53cf95
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2025-07-04 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 14:19 [PATCH] arm64: Unconditionally select CONFIG_JUMP_LABEL Marc Zyngier
2025-06-13 14:47 ` Mark Rutland
2025-06-16 11:30 ` Will Deacon
2025-07-04 17:44 ` Will Deacon [this message]
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=175163687202.1322627.833974757174570861.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=aneesh.kumar@kernel.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=smostafa@google.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