[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169175309213.3101777.18103736933706442373.b4-ty@kernel.org>
Date: Fri, 11 Aug 2023 12:44:52 +0100
From: Will Deacon <will@...nel.org>
To: Mark Brown <broonie@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
Shuah Khan <shuah@...nel.org>
Cc: kernel-team@...roid.com, Will Deacon <will@...nel.org>,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] kselftest/arm64: Size sycall-abi buffers for the actual maximum VL
On Thu, 10 Aug 2023 12:39:19 +0100, Mark Brown wrote:
> Our ABI opts to provide future proofing by defining a much larger
> SVE_VQ_MAX than the architecture actually supports. Since we use
> this define to control the size of our vector data buffers this results
> in a lot of overhead when we initialise which can be a very noticable
> problem in emulation, we fill buffers that are orders of magnitude
> larger than we will ever actually use even with virtual platforms that
> provide the full range of architecturally supported vector lengths.
>
> [...]
Applied to arm64 (for-next/selftests), thanks!
[1/1] kselftest/arm64: Size sycall-abi buffers for the actual maximum VL
https://git.kernel.org/arm64/c/358b763ee64b
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists