From:   Catalin Marinas <catalin.marinas@arm.com>
To:     Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>,
        Mark Brown <broonie@kernel.org>
Cc:     linux-arm-kernel@lists.infradead.org,
        linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kselftest/arm64: Limit the maximum VL we try to set via ptrace
Date:   Tue, 31 Jan 2023 16:28:25 +0000
Message-Id: <167518250322.582901.15647652127648162465.b4-ty@arm.com>
In-Reply-To: <20230111-arm64-kselftest-ptrace-max-vl-v1-1-8167f41d1ad8@kernel.org>
References: <20230111-arm64-kselftest-ptrace-max-vl-v1-1-8167f41d1ad8@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 11 Jan 2023 15:02:41 +0000, Mark Brown wrote:
> When SVE was initially merged we chose to export the maximum VQ in the ABI
> as being 512, rather more than the architecturally supported maximum of 16.
> For the ptrace tests this results in us generating a lot of test cases and
> hence log output which are redundant since a system couldn't possibly
> support them. Instead only check values up to the current architectural
> limit, plus one more so that we're covering the constraining of higher
> vector lengths.
> 
> [...]

Applied to arm64 (for-next/kselftest), thanks!

[1/1] kselftest/arm64: Limit the maximum VL we try to set via ptrace
      https://git.kernel.org/arm64/c/89ff30b9b720

-- 
Catalin