From: Mark Brown <broonie@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
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, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/6] kselftest/arm64: Corrupt P15 in the irritator when testing SSVE
Date: Wed, 6 Nov 2024 12:46:10 +0000 [thread overview]
Message-ID: <36fb49f5-55d8-4890-a8d4-d2cba67a9185@sirena.org.uk> (raw)
In-Reply-To: <ZytSnBSk4r81a3z1@J2N7QTR9R3>
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
On Wed, Nov 06, 2024 at 11:27:24AM +0000, Mark Rutland wrote:
> > +#ifndef SSVE
> > // And FFR
> > wrffr p15.b
> > #endif
> Both RDFFR and WRFFR are illegal in streaming mode unless FEAT_FA64 is
> implemented and enabled, so we cannot use DRFFR in the SSVE case.
Indeed, I'm surprised that managed to pass my testing...
> Is there a different instruction we can use?
We could just trash p0 with something like a load or add.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-11-06 12:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 20:38 [PATCH 0/6] kselftest/arm64: Test floating point signal context restore in fp-stress Mark Brown
2024-10-23 20:38 ` [PATCH 1/6] kselftest/arm64: Correct misleading comments on fp-stress irritators Mark Brown
2024-11-06 11:29 ` Mark Rutland
2024-10-23 20:38 ` [PATCH 2/6] kselftest/arm64: Remove unused ADRs from irritator handlers Mark Brown
2024-11-06 11:29 ` Mark Rutland
2024-10-23 20:38 ` [PATCH 3/6] kselftest/arm64: Corrupt P15 in the irritator when testing SSVE Mark Brown
2024-11-06 11:27 ` Mark Rutland
2024-11-06 12:46 ` Mark Brown [this message]
2024-10-23 20:38 ` [PATCH 4/6] kselftest/arm64: Implement irritators for ZA and ZT Mark Brown
2024-11-06 11:31 ` Mark Rutland
2024-10-23 20:38 ` [PATCH 5/6] kselftest/arm64: Provide a SIGUSR1 handler in the kernel mode FP stress test Mark Brown
2024-11-06 11:32 ` Mark Rutland
2024-10-23 20:38 ` [PATCH 6/6] kselftest/arm64: Test signal handler state modification in fp-stress Mark Brown
2024-11-06 11:33 ` Mark Rutland
2024-10-28 14:26 ` [PATCH 0/6] kselftest/arm64: Test floating point signal context restore " Mark Rutland
2024-10-28 15:38 ` Mark Brown
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=36fb49f5-55d8-4890-a8d4-d2cba67a9185@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=shuah@kernel.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
all inboxes | Powered by JetHome®