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:   Thu, 20 Jul 2023 13:27:10 +0100
From:   Mark Brown <broonie@kernel.org>
To:     Will Deacon <will@kernel.org>
Cc:     Catalin Marinas <catalin.marinas@arm.com>,
        Shuah Khan <shuah@kernel.org>,
        David Spickett <David.Spickett@arm.com>,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
        linux-kselftest@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/3] arm64/fpsimd: Ensure SME storage is allocated after
 SVE VL changes
Message-ID: <3ce4fc14-bd43-47e9-aa37-59bb3cd5d051@sirena.org.uk>
References: <20230713-arm64-fix-sve-sme-vl-change-v1-0-129dd8611413@kernel.org>
 <20230713-arm64-fix-sve-sme-vl-change-v1-1-129dd8611413@kernel.org>
 <20230720105235.GD11034@willie-the-truck>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="CyMXBdFoH12etnuE"
Content-Disposition: inline
In-Reply-To: <20230720105235.GD11034@willie-the-truck>
Precedence: bulk


--CyMXBdFoH12etnuE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Jul 20, 2023 at 11:52:36AM +0100, Will Deacon wrote:
> On Thu, Jul 13, 2023 at 09:06:04PM +0100, Mark Brown wrote:

> > Since the ABI does not specify that changing the SVE vector length disturbs
> > SME state, and since SVE code may not be aware of SME code in the process,
> > we shouldn't simply discard any ZA state. Instead immediately reallocate
> > the storage for SVE if SME is active, and disable SME if we change the SVE
> > vector length while there is no SME state active.

> What is the advantage of keep the old behaviour in this case? In other
> words, if it's acceptable to reallocate the state when SME is active, why
> not just reallocate in all cases?

It was minimising the changes to the status quo given how attached
people often are to these things.

--CyMXBdFoH12etnuE
Content-Type: application/pgp-signature; name="signature.asc"

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

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmS5KB4ACgkQJNaLcl1U
h9C+0gf/fQxZuh51kIYByTPW3QLeYr1gzvXo8eFWKQxVOYg96BpcLaqbrocw6ZLg
E0VA1/CrGB56VUq99z4VY0JUrqFoupiFJE5M5MihIAUi/0PPH9LsvzvuXuIAnrK4
CmqsOfSQTbsXhntG34dq3UkcK7VZlbK4iSZsaKig3BLtIWHBVJ1WvLpnxEkVu0Mv
+qJM4GDgPeIXRKiMcxT6+Gd96Vza5VFUemOFSO9BGW5XzQE7Ix+NpT99XvE0MtwJ
mTVS7V3g0F+19U08hExwfgrKS1ybUONPOqncDhwLdghsLFFOeW8WI1ttxw26afX8
UO1YvtblScSAt6Aex+N4yBujBbHMaA==
=NOme
-----END PGP SIGNATURE-----

--CyMXBdFoH12etnuE--