Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 15 Nov 2022 10:58:00 +0000
From:   Mark Brown <broonie@kernel.org>
To:     Arnd Bergmann <arnd@arndb.de>
Cc:     Naresh Kamboju <naresh.kamboju@linaro.org>,
        open list <linux-kernel@vger.kernel.org>,
        linux-stable <stable@vger.kernel.org>,
        lkft-triage@lists.linaro.org,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Ard Biesheuvel <ardb@kernel.org>
Subject: Re: WARNING: CPU: 0 PID: 1111 at arch/arm64/kernel/fpsimd.c:464
 fpsimd_save+0x170/0x1b0
Message-ID: <Y3NwuOKJXudb9K30@sirena.org.uk>
References: <CA+G9fYuXG7Rh_A8W1NRVWbgWjozwzxzQY7tYw7bA4NsCuSovMg@mail.gmail.com>
 <97c413be-1a24-4447-b7ea-fa81a3170765@app.fastmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="Q2Os0hM+U3KKHspW"
Content-Disposition: inline
In-Reply-To: <97c413be-1a24-4447-b7ea-fa81a3170765@app.fastmail.com>
Precedence: bulk


--Q2Os0hM+U3KKHspW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Nov 15, 2022 at 09:22:53AM +0100, Arnd Bergmann wrote:

> Have you tried what happens if you run the same thing on an x86
> machine? I would expect them to behave the same way, but it's
> possible something goes wrong with the guest CPU if this ends
> up using some (but not all) of the logic from KVM that would
> use '-cpu host' instead of '-cpu max'. Note that the Neoverse
> CPU in the Altra machine does not support SVE.

I'm finding it hard to think of a failure pattern that would
make it through VL discovery then fail at runtime but also not
obviously trigger any issues in syscall-abi...

> Other things you could easily try would use the same command
> line as above, with the possible combinations of '-cpu host'
> (replacing -cpu max) and '-enable-kvm'. Do you always get
> the same result?

The machine parameter accel={tcg,kvm} is useful for forcing a
specific backend - it's probably wise to force TCG if you might
be running on a job on a native architecture.

BTW there's some other funky stuff going on with that job, the
syscall-abi test is stopped with a timeout after 45 seconds (as
is sve-ptrace) which appears to be coming from a harness
somewhere.  The selection of FP tests run seems to miss fp-stress
too.

--Q2Os0hM+U3KKHspW
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmNzcLcACgkQJNaLcl1U
h9DlGQf/d9Fj8SoOkkYluJqJi8BFS1IA4U8ObGdL1Ntw4YR2qlhSMkgKBMVVsLWp
NxdrmmzfbyfO8qPsNP85lvZlAu9z7ddDlBorMzVlFAVwZOkydzT7JiYEy44y7o/0
F6qFLXXO5l4fYsmDBvmglXiPXitFuQTgzNDIyhx1ETJErBaBzQiRpI45sCqO2Zju
lZnJgH86mqm0G+mVkTd1gsx2iX9QYxUYoilNWGozV44N1zoz/8KH+KtbvtE2U7Au
DCgOuc9WF/zqaEJ8Xi4dkHSHGidHC4rbkjyh63ANWpKZPyXT4czxC+xsBe1GJdOv
7z7/zaxbY4FNze1s8LpBHMWLWE0rtg==
=pVs/
-----END PGP SIGNATURE-----

--Q2Os0hM+U3KKHspW--