From: sashiko-bot@kernel.org
To: "Tomohiro Misono" <misono.tomohiro@fujitsu.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v3 5/5] arm64: Add workaround to replace WFE with NOP for FUJITSU-MONAKA Erratum E#030004
Date: Thu, 19 Nov 2026 09:19:24 +0000 [thread overview]
Message-ID: <sashiko-outbox-222811@kernel.org> (raw)
In-Reply-To: <20261119-monaka-fix-for-upstream-v3-5-057df4d2ca3c@fujitsu.com>
> This option adds a workaround for FUJITSU-MONAKA erratum E#030004.
>
> On affected CPUs, if a wake-up event generated by clearing the
> global exclusive monitor or by a SEV instruction arrives in the
> same cycle as a WFE instruction commits, the CPU may fail to
> advance the program counter and re-execute the same WFE
> instruction. If no further wake-up event occurs, the CPU may
> remain waiting indefinitely (for example, in spinlock code).
> This may cause a system hang before the generic timer event stream
> is enabled. WFI, WFIT, and WFET instructions are not affected.
>
> After the event stream is enabled (shortly after the secondary CPU
> bring-up), event stream could wake up affected cores.
> However, in order to prevent the condition during secondary CPU
> bring-up, the workaround replaces all WFE instructions in host kernel
> code with NOP using the boot alternative framework before the secondary
> CPU bring-up on the MONAKA CPU.
>
> Note that there is no need to take care of WFE usage in Host EL0 and
> VHE Guest since if event stream is enabled in Host EL2, the event
> reaches to every ELx & world. This effectively means FUJITSU-MONAKA
> does not guarantee disabling event stream
> (clocksource.arm_arch_timer.evtstrm=0) nor running nVHE guests
> (kvm-arm.mode=nvhe/protected), although these configurations
> are not rejected by this patch.
>
> This only affects FUJITSU-MONAKA CPUs.
>
> Assisted-by: LLM
> Signed-off-by: Tomohiro Misono <misono.tomohiro@fujitsu.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261119-monaka-fix-for-upstream-v3-0-057df4d2ca3c@fujitsu.com?part=5
prev parent reply other threads:[~2026-11-19 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 9:04 [PATCH v3 0/5] arm64: Add workarounds for FUJITSU-MONAKA CPU Tomohiro Misono
2026-11-19 9:04 ` [PATCH v3 1/5] arm64: cputype: Add FUJITSU MONAKA definition Tomohiro Misono
2026-11-19 9:09 ` sashiko-bot
2026-11-19 9:04 ` [PATCH v3 2/5] arm64: tlb: Add tlbi workaround for FUJITSU-MONAKA Erratum E#030001 Tomohiro Misono
2026-11-19 9:30 ` sashiko-bot
2026-11-19 9:04 ` [PATCH v3 3/5] perf: arm_pmu: Add workaround for FUJITSU-MONAKA Erratum E#030002 Tomohiro Misono
2026-11-19 9:16 ` sashiko-bot
2026-11-19 9:04 ` [PATCH v3 4/5] irqchip/gicv3: Add workaround for FUJITSU-MONAKA Erratum E#030003 Tomohiro Misono
2026-11-19 9:21 ` sashiko-bot
2026-11-19 9:04 ` [PATCH v3 5/5] arm64: Add workaround to replace WFE with NOP for FUJITSU-MONAKA Erratum E#030004 Tomohiro Misono
2026-11-19 9:19 ` sashiko-bot [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=sashiko-outbox-222811@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=misono.tomohiro@fujitsu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox