From: Dave Martin <Dave.Martin@arm.com>
To: Will Deacon <will@kernel.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Brown <broonie@kernel.org>,
linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/6] selftests: arm64: Add floating point selftests
Date: Tue, 1 Sep 2020 16:27:17 +0100 [thread overview]
Message-ID: <20200901152716.GZ6642@arm.com> (raw)
In-Reply-To: <20200901132159.GA3579@willie-the-truck>
On Tue, Sep 01, 2020 at 02:21:59PM +0100, Will Deacon wrote:
> On Mon, Aug 31, 2020 at 03:45:46PM -0600, Shuah Khan wrote:
> > On 8/19/20 5:48 AM, Mark Brown wrote:
> > > This series imports a series of tests for FPSIMD and SVE originally
> > > written by Dave Martin to the tree. Since these extensions have some
> > > overlap in terms of register usage and must sometimes be tested together
> > > they're dropped into a single directory. I've adapted some of the tests
> > > to run within the kselftest framework but there are also some stress
> > > tests here that are intended to be run as soak tests so aren't suitable
> > > for running by default and are mostly just integrated with the build
> > > system. There doesn't seem to be a more suitable home for those stress
> > > tests and they are very useful for work on these areas of the code so it
> > > seems useful to have them somewhere in tree.
> > >
> > > v2: Rebased onto v5.9-rc1
> > >
> > > Mark Brown (6):
> > > selftests: arm64: Test case for enumeration of SVE vector lengths
> > > selftests: arm64: Add test for the SVE ptrace interface
> > > selftests: arm64: Add stress tests for FPSMID and SVE context
> > > switching
> > > selftests: arm64: Add utility to set SVE vector lengths
> > > selftests: arm64: Add wrapper scripts for stress tests
> > > selftests: arm64: Add build and documentation for FP tests
> >
> > Patches look good to me from selftests perspective. My acked by
> > for these patches to go through arm64.
> >
> > Acked-by: Shuah Khan <skhan@linuxfoundation.org>
>
> Thanks, Shuah.
>
> > If you would like me to take these through kselftest tree, give
> > me your Acks. I can queue these up for 5.10-rc1
>
> Given there are a few arm64 kselftests series pending at the moment, I'll
> queue them in the arm64 tree, but on their own branch in case you end up
> needing to pull it in as well. I'll drop you a note once I've done that
> (I'm just starting to queue stuff this week).
>
> Will
FWIW,
Acked-by: Dave Martin <Dave.Martin@arm.com>
I haven't gone through the integration in detail, but nothing leaps out
as disastrously wrong.
I'm not sure how useful these tests are to people in general, but
they've been valuable for maintaining the FP context switch code on
arm64. I think it makes sense to keep them alongside the kernel so that
they don't get get lost.
Cheers
---Dave
next prev parent reply other threads:[~2020-09-01 16:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 11:48 [PATCH v2 0/6] selftests: arm64: Add floating point selftests Mark Brown
2020-08-19 11:48 ` [PATCH v2 1/6] selftests: arm64: Test case for enumeration of SVE vector lengths Mark Brown
2020-08-19 11:48 ` [PATCH v2 2/6] selftests: arm64: Add test for the SVE ptrace interface Mark Brown
2020-08-19 11:48 ` [PATCH v2 3/6] selftests: arm64: Add stress tests for FPSMID and SVE context switching Mark Brown
2020-08-19 11:48 ` [PATCH v2 4/6] selftests: arm64: Add utility to set SVE vector lengths Mark Brown
2020-08-19 11:48 ` [PATCH v2 5/6] selftests: arm64: Add wrapper scripts for stress tests Mark Brown
2020-08-19 11:48 ` [PATCH v2 6/6] selftests: arm64: Add build and documentation for FP tests Mark Brown
2020-09-01 15:38 ` Dave Martin
2020-09-01 15:47 ` Mark Brown
2020-09-01 16:06 ` Dave Martin
2020-08-31 21:45 ` [PATCH v2 0/6] selftests: arm64: Add floating point selftests Shuah Khan
2020-09-01 13:21 ` Will Deacon
2020-09-01 15:27 ` Dave Martin [this message]
2020-09-18 16:17 ` Will Deacon
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=20200901152716.GZ6642@arm.com \
--to=dave.martin@arm.com \
--cc=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