From: Will Deacon <will@kernel.org>
To: Joey Gouly <joey.gouly@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, nd@arm.com,
catalin.marinas@arm.com
Subject: Re: [PATCH v1 2/2] selftests/arm64: add HWCAP2_HBC test
Date: Tue, 1 Aug 2023 16:09:14 +0100 [thread overview]
Message-ID: <20230801150914.GH26253@willie-the-truck> (raw)
In-Reply-To: <20230801100008.3125054-3-joey.gouly@arm.com>
On Tue, Aug 01, 2023 at 11:00:08AM +0100, Joey Gouly wrote:
> Add a test for the newly added HWCAP2_HBC.
>
> Signed-off-by: Joey Gouly <joey.gouly@arm.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> ---
> tools/testing/selftests/arm64/abi/hwcap.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/tools/testing/selftests/arm64/abi/hwcap.c b/tools/testing/selftests/arm64/abi/hwcap.c
> index d4ad813fed10..296102cd9192 100644
> --- a/tools/testing/selftests/arm64/abi/hwcap.c
> +++ b/tools/testing/selftests/arm64/abi/hwcap.c
> @@ -208,6 +208,13 @@ static void svebf16_sigill(void)
> asm volatile(".inst 0x658aa000" : : : "z0");
> }
>
> +static void hbc_sigill(void)
> +{
> + /* BC.EQ +4 */
> + asm volatile("cmp xzr, xzr\n"
> + ".inst 0x54000030" : : :);
> +}
Do you need a "cc" clobber here, or is that implicit somehow?
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-01 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 10:00 [PATCH v1 0/2] HWCAP for FEAT_HBC Joey Gouly
2023-08-01 10:00 ` [PATCH v1 1/2] arm64: add HWCAP for FEAT_HBC (hinted conditional branches) Joey Gouly
2023-08-01 15:12 ` Will Deacon
2023-08-02 11:54 ` Joey Gouly
2023-08-04 13:19 ` Will Deacon
2023-08-01 10:00 ` [PATCH v1 2/2] selftests/arm64: add HWCAP2_HBC test Joey Gouly
2023-08-01 15:09 ` Will Deacon [this message]
2023-08-01 15:26 ` Joey Gouly
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=20230801150914.GH26253@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nd@arm.com \
/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