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;
From:   Will Deacon <will@kernel.org>
To:     Mark Brown <broonie@kernel.org>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Shuah Khan <shuah@kernel.org>
Cc:     kernel-team@android.com, Will Deacon <will@kernel.org>,
        linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
        linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] kselftest/arm64: Size sycall-abi buffers for the actual maximum VL
Date:   Fri, 11 Aug 2023 12:44:52 +0100
Message-Id: <169175309213.3101777.18103736933706442373.b4-ty@kernel.org>
In-Reply-To: <20230810-arm64-syscall-abi-perf-v1-1-6a0d7656359c@kernel.org>
References: <20230810-arm64-syscall-abi-perf-v1-1-6a0d7656359c@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

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