[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aBT9yiaLF9LisLR6@arm.com>
Date: Fri, 2 May 2025 18:15:54 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: Yeoreum Yun <yeoreum.yun@....com>
Cc: will@...nel.org, broonie@...nel.org, anshuman.khandual@....com,
joey.gouly@....com, yury.khrustalev@....com, maz@...nel.org,
oliver.upton@...ux.dev, frederic@...nel.org,
shmeerali.kolothum.thodi@...wei.com, james.morse@....com,
mark.rutland@....com, huangxiaojia2@...wei.com,
akpm@...ux-foundation.org, surenb@...gle.com, robin.murphy@....com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, nd@....com
Subject: Re: [PATCH v3 3/3] tools/kselftest: add MTE_FAR hwcap test
On Thu, Apr 10, 2025 at 08:47:21AM +0100, Yeoreum Yun wrote:
> diff --git a/tools/testing/selftests/arm64/abi/hwcap.c b/tools/testing/selftests/arm64/abi/hwcap.c
> index 35f521e5f41c..a539eeb0bfc0 100644
> --- a/tools/testing/selftests/arm64/abi/hwcap.c
> +++ b/tools/testing/selftests/arm64/abi/hwcap.c
> @@ -1098,6 +1098,12 @@ static const struct hwcap_data {
> .sigill_fn = hbc_sigill,
> .sigill_reliable = true,
> },
> + {
> + .name = "MTE_FAR",
> + .at_hwcap = AT_HWCAP3,
> + .hwcap_bit = HWCAP3_MTE_FAR,
> + .cpuinfo = "mte_far",
> + },
> };
This is all good but I'd also like to see a test to check the FAR_EL1
bits are actually exposed to the signal handler when the hwcap is
present.
--
Catalin
Powered by blists - more mailing lists