From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>, Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 0/6] kselftest/arm64: SVE signal handling tests
Date: Mon, 23 Aug 2021 13:58:35 +0100 [thread overview]
Message-ID: <162972351131.16315.329516738132119653.b4-ty@arm.com> (raw)
In-Reply-To: <20210819134245.13935-1-broonie@kernel.org>
On Thu, 19 Aug 2021 14:42:39 +0100, Mark Brown wrote:
> Currently we have no real tests for SVE signal handling (though the
> stress test does trigger the code paths as it regularly sends signals to
> the test processes). Add some basic coverage, this is very much
> incomplete but it's more coverage than we currently have, a TODO file is
> included with some omissions that occurred to me.
>
> Mark Brown (6):
> kselftest/arm64: signal: Add SVE to the set of features we can check
> for
> kselftest/arm64: signal: Support signal frames with SVE register data
> kselftest/arm64: signal: Check SVE signal frame shows expected vector
> length
> kselftest/arm64: signal: Verify that signals can't change the SVE
> vector length
> kselftest/arm64: signal: Add test case for SVE register state in
> signals
> kselftest/arm64: signal: Add a TODO list for signal handling tests
>
> [...]
Applied to arm64 (for-next/kselftest), thanks!
[1/6] kselftest/arm64: signal: Add SVE to the set of features we can check for
https://git.kernel.org/arm64/c/d4e4dc4fab68
[2/6] kselftest/arm64: signal: Support signal frames with SVE register data
https://git.kernel.org/arm64/c/ace19b1845a5
[3/6] kselftest/arm64: signal: Check SVE signal frame shows expected vector length
https://git.kernel.org/arm64/c/c1f67a19c12e
[4/6] kselftest/arm64: signal: Verify that signals can't change the SVE vector length
https://git.kernel.org/arm64/c/d25ac50ce8f7
[5/6] kselftest/arm64: signal: Add test case for SVE register state in signals
https://git.kernel.org/arm64/c/5262b216f4a9
[6/6] kselftest/arm64: signal: Add a TODO list for signal handling tests
https://git.kernel.org/arm64/c/fa5ca80db89e
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-08-23 13:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 13:42 [PATCH v1 0/6] kselftest/arm64: SVE signal handling tests Mark Brown
2021-08-19 13:42 ` [PATCH v1 1/6] kselftest/arm64: signal: Add SVE to the set of features we can check for Mark Brown
2021-08-19 13:42 ` [PATCH v1 2/6] kselftest/arm64: signal: Support signal frames with SVE register data Mark Brown
2021-08-19 13:42 ` [PATCH v1 3/6] kselftest/arm64: signal: Check SVE signal frame shows expected vector length Mark Brown
2021-08-19 13:42 ` [PATCH v1 4/6] kselftest/arm64: signal: Verify that signals can't change the SVE " Mark Brown
2021-08-19 13:42 ` [PATCH v1 5/6] kselftest/arm64: signal: Add test case for SVE register state in signals Mark Brown
2021-08-19 13:42 ` [PATCH v1 6/6] kselftest/arm64: signal: Add a TODO list for signal handling tests Mark Brown
2021-08-23 12:58 ` Catalin Marinas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162972351131.16315.329516738132119653.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.