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:   Mark Brown <broonie@kernel.org>
Subject: [PATCH 0/2] kselftest/arm64: Minor SME signals test additions
Date:   Fri, 20 Jan 2023 12:04:08 +0000
Message-Id: <20230117-arm64-test-ssve-za-v1-0-203c00150154@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To:     Catalin Marinas <catalin.marinas@arm.com>,
        Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>
Cc:     linux-arm-kernel@lists.infradead.org,
        linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
        Mark Brown <broonie@kernel.org>
Precedence: bulk

While discussing the SME signal handling support I realised that
we were not verifying that SVE_SIG_FLAG_SM is set for streaming
SVE, and not explicitly covering the case where we are both in
streaming mode and have ZA enabled.  Add coverage of these cases,
I didn't find any problems running these new tests.

To: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will@kernel.org>
To: Shuah Khan <shuah@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-kselftest@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Mark Brown <broonie@kernel.org>

---
Mark Brown (2):
      kselftest/arm64: Verify that SSVE signal context has SVE_SIG_FLAG_SM set
      kselftest/arm64: Verify simultaneous SSVE and ZA context generation

 .../selftests/arm64/signal/testcases/ssve_regs.c   |   5 +
 .../arm64/signal/testcases/ssve_za_regs.c          | 162 +++++++++++++++++++++
 2 files changed, 167 insertions(+)
---
base-commit: b7bfaa761d760e72a969d116517eaa12e404c262
change-id: 20230117-arm64-test-ssve-za-7128c0ce8dc9

Best regards,
-- 
Mark Brown <broonie@kernel.org>