From: Shuah Khan <skhan@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Shuah Khan <shuah@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
kvmarm@lists.linux.dev, linux-kselftest@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2 9/9] kselftest/arm64: Add 2024 dpISA extensions to hwcap test
Date: Thu, 31 Oct 2024 12:03:20 -0600 [thread overview]
Message-ID: <4703b646-3df4-43d3-ad75-92a38f5574c3@linuxfoundation.org> (raw)
In-Reply-To: <20241030-arm64-2024-dpisa-v2-9-b6601a15d2a5@kernel.org>
On 10/30/24 09:34, Mark Brown wrote:
> We don't actually test SIGILL generation for CMPBR since the need to
> branch makes it a pain to generate and the SIGILL detection would be
> unreliable anyway. Since this should be very unusual we provide a stub
> function rather than supporting a missing function.
>
> The sigill functions aren't well sorted in the file so the ordering is a
> bit random.
This is talking about the one that isn't implemented. Can you add
a sentence or two about the ones that this patch adds?
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> tools/testing/selftests/arm64/abi/hwcap.c | 273 +++++++++++++++++++++++++++++-
> 1 file changed, 271 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/arm64/abi/hwcap.c b/tools/testing/selftests/arm64/abi/hwcap.c
> index f2d6007a2b983eba77a880ec7e614396a6cb1377..beb380bc09b0d07269a85a60e5d2977367740473 100644
> --- a/tools/testing/selftests/arm64/abi/hwcap.c
> +++ b/tools/testing/selftests/arm64/abi/hwcap.c
> @@ -46,6 +46,12 @@ static void atomics_sigill(void)
> asm volatile(".inst 0xb82003ff" : : : );
> }
>
> +static void cmpbr_sigill(void)
> +{
> + /* Not implemented, too complicated and unreliable anyway */
> +}
> +
You anticpated "not used" messages looks like. I see that
this gets called - thanks.
Looks good to me. With the change to change log
Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
thanks,
-- Shuah
prev parent reply other threads:[~2024-10-31 18:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 15:34 [PATCH v2 0/9] arm64: Support 2024 dpISA extensions Mark Brown
2024-10-30 15:34 ` [PATCH v2 1/9] arm64/sysreg: Update ID_AA64PFR2_EL1 to DDI0601 2024-09 Mark Brown
2024-10-30 15:34 ` [PATCH v2 2/9] arm64/sysreg: Update ID_AA64ISAR3_EL1 " Mark Brown
2024-10-30 15:34 ` [PATCH v2 3/9] arm64/sysreg: Update ID_AA64FPFR0_EL1 " Mark Brown
2024-10-30 15:34 ` [PATCH v2 4/9] arm64/sysreg: Update ID_AA64ZFR0_EL1 " Mark Brown
2024-10-30 15:34 ` [PATCH v2 5/9] arm64/sysreg: Update ID_AA64SMFR0_EL1 " Mark Brown
2024-10-30 15:34 ` [PATCH v2 6/9] arm64/sysreg: Update ID_AA64ISAR2_EL1 " Mark Brown
2024-10-30 15:34 ` [PATCH v2 7/9] arm64/hwcap: Describe 2024 dpISA extensions to userspace Mark Brown
2024-10-30 15:34 ` [PATCH v2 8/9] KVM: arm64: Allow control of dpISA extensions in ID_AA64ISAR3_EL1 Mark Brown
2024-10-30 15:34 ` [PATCH v2 9/9] kselftest/arm64: Add 2024 dpISA extensions to hwcap test Mark Brown
2024-10-31 18:03 ` Shuah Khan [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=4703b646-3df4-43d3-ad75-92a38f5574c3@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=shuah@kernel.org \
--cc=suzuki.poulose@arm.com \
--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