From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Mark Brown <broonie@kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <linuxarm@huawei.com>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Warning on SME when manually onlining CPUs late.
Date: Thu, 27 Jul 2023 11:21:22 +0100 [thread overview]
Message-ID: <20230727112122.00000810@huawei.com> (raw)
Hi Mark
Hit this due to a silly config error on a QEMU TCG test but seemed worth asking about
as I'm buried in other stuff and no time to investigate further for a few weeks.
Test probably could be simplified but it's more or less vanilla upstream QEMU with
-cpu max -smp 8 and kernel command line with maxcpus=4
echo 1 > /sys/bus/cpu/devices/cpu4/online
CPU features: SANITY CHECK: Unexpected variation in SYS_SMCR_EL1. Boot CPU: 0x0000000000000f, CPU4: 0x0000008000000f
CPU features: Unsupported CPU feature variation detected.
If this is already well known, then sorry for noise. I've not been paying much attention
to the SME work.
Looks like the FA64 bit isn't set for the CPU state of the boot CPU that is being compared
- I guess a stale record somewhere being used for the comparison?
Could be an issue on QEMU side I guess - though from a quick look it all seemed to be
correct there. Just in case +CC Richard.
Jonathan
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-07-27 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 10:21 Jonathan Cameron [this message]
2023-07-27 17:02 ` Warning on SME when manually onlining CPUs late Richard Henderson
2023-07-27 17:31 ` Mark Brown
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=20230727112122.00000810@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxarm@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).