From: Mark Brown <broonie@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v1 2/3] kselftest/arm64: Remove assumption that tasks start FPSIMD only
Date: Wed, 9 Mar 2022 22:00:23 +0000 [thread overview]
Message-ID: <Yikjd4s/05G9UFe0@sirena.org.uk> (raw)
In-Reply-To: <5f892a90-6870-001b-d265-885f49a738ce@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
On Wed, Mar 09, 2022 at 02:36:26PM -0700, Shuah Khan wrote:
> On 3/9/22 4:59 AM, Mark Brown wrote:
> > Currently the sve-ptrace test for setting and reading FPSIMD data assumes
> > that the child will start off in FPSIMD only mode and that it can use this
> > to read some FPSIMD mode SVE ptrace data, skipping the test if it can't.
> > -#define FPSIMD_TESTS 3
> > +#define FPSIMD_TESTS 2
> Looks like there is one less test now?
Yes, the initial read which we assumed would return FPSIMD data was
being reported as a distinct test.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-03-09 22:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 11:59 [PATCH v1 0/3] kselftest/arm64: Test ptrace writing via FPSIMD and reading via SVE Mark Brown
2022-03-09 11:59 ` [PATCH v1 1/3] kselftest/arm64: Fix comment for ptrace_sve_get_fpsimd_data() Mark Brown
2022-03-09 21:35 ` Shuah Khan
2022-03-09 11:59 ` [PATCH v1 2/3] kselftest/arm64: Remove assumption that tasks start FPSIMD only Mark Brown
2022-03-09 21:36 ` Shuah Khan
2022-03-09 22:00 ` Mark Brown [this message]
2022-03-09 11:59 ` [PATCH v1 3/3] kselftest/arm64: Validate setting via FPSIMD and read via SVE regsets Mark Brown
2022-03-09 21:37 ` Shuah Khan
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=Yikjd4s/05G9UFe0@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox