From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Kohei Enju <enju.kohei@fujitsu.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Sami Mujawar <sami.mujawar@arm.com>,
Steven Price <steven.price@arm.com>,
Gavin Shan <gshan@redhat.com>
Subject: Re: [PATCH v3] virt: arm-cca-guest: use migrate_disable() for attestation token requests
Date: Wed, 22 Jul 2026 09:23:21 +0100 [thread overview]
Message-ID: <178467175320.116388.3560341069343395580.b4-ty@kernel.org> (raw)
In-Reply-To: <20260612111007.49434-1-enju.kohei@fujitsu.com>
On Fri, 12 Jun 2026 20:09:21 +0900, Kohei Enju wrote:
> The RSI attestation token init and continue calls must be issued from
> the same CPU. arm_cca_report_new() currently snapshots the CPU number
> and uses smp_call_function_single() to issue those calls on that CPU.
>
> With CONFIG_DEBUG_PREEMPT=y, the smp_processor_id() call used for the
> snapshot triggers a debug splat [0] because it runs in preemptible
> context. The snapshot does not pin the task to that CPU; it is only used
> to choose the target CPU for smp_call_function_single(), which can fail
> if that CPU is no longer available.
>
> [...]
Applied to arm64 (for-next/coco), thanks!
[1/1] virt: arm-cca-guest: use migrate_disable() for attestation token requests
https://git.kernel.org/arm64/c/24f55f511b9e
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-07-22 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 11:09 Kohei Enju
2026-07-03 6:28 ` Kohei Enju
2026-07-03 14:30 ` Steven Price
2026-07-09 4:05 ` Gavin Shan
2026-07-09 17:48 ` Suzuki K Poulose
2026-07-22 8:23 ` 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=178467175320.116388.3560341069343395580.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=enju.kohei@fujitsu.com \
--cc=gshan@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sami.mujawar@arm.com \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.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
all inboxes | Powered by JetHome®