From: Yury Khrustalev <yury.khrustalev@arm.com>
To: Yeoreum Yun <yeoreum.yun@arm.com>
Cc: <catalin.marinas@arm.com>, <will@kernel.org>,
<broonie@kernel.org>, <anshuman.khandual@arm.com>,
<joey.gouly@arm.com>, <maz@kernel.org>, <oliver.upton@linux.dev>,
<frederic@kernel.org>, <shameerali.kolothum.thodi@huawei.com>,
<james.morse@arm.com>, <mark.rutland@arm.com>,
<huangxiaojia2@huawei.com>, <akpm@linux-foundation.org>,
<surenb@google.com>, <robin.murphy@arm.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<nd@arm.com>
Subject: Re: [PATCH v2 1/3] arm64: add FEAT_MTE_TAGGED_FAR feature
Date: Mon, 7 Apr 2025 13:04:24 +0100 [thread overview]
Message-ID: <Z_O_SHiQwr-ZWw52@arm.com> (raw)
In-Reply-To: <20250403172758.67106-2-yeoreum.yun@arm.com>
On Thu, Apr 03, 2025 at 06:27:56PM +0100, Yeoreum Yun wrote:
> Add FEAT_MTE_TAGGED_FAR cpucap which makes FAR_ELx report
> all non-address bits on a synchronous MTE tag check fault since Armv8.9
>
> Signed-off-by: Yeoreum Yun <yeoreum.yun@arm.com>
> ---
> ...
> arch/arm64/include/asm/hwcap.h | 1 +
> ...
>
> diff --git a/arch/arm64/include/uapi/asm/hwcap.h b/arch/arm64/include/uapi/asm/hwcap.h
> index 705a7afa8e58..7d22527a7975 100644
> --- a/arch/arm64/include/uapi/asm/hwcap.h
> +++ b/arch/arm64/include/uapi/asm/hwcap.h
> @@ -143,5 +143,6 @@
> /*
> * HWCAP3 flags - for AT_HWCAP3
> */
> +#define HWCAP3_MTE_FAR (1UL << 0)
Acked-by: Yury Khrustalev <yury.khrustalev@arm.com>
next prev parent reply other threads:[~2025-04-07 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 17:27 [PATCH v2 0/3] support FEAT_MTE_TAGGED_FAR feature Yeoreum Yun
2025-04-03 17:27 ` [PATCH v2 1/3] arm64: add " Yeoreum Yun
2025-04-07 12:04 ` Yury Khrustalev [this message]
2025-04-03 17:27 ` [PATCH v2 2/3] arm64/mm/fault: use original FAR_EL1 value when ARM64_MTE_FAR is supported Yeoreum Yun
2025-04-03 17:27 ` [PATCH v2 3/3] tools/kselftest: add MTE_FAR hwcap test Yeoreum Yun
2025-04-04 15:57 ` 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=Z_O_SHiQwr-ZWw52@arm.com \
--to=yury.khrustalev@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=frederic@kernel.org \
--cc=huangxiaojia2@huawei.com \
--cc=james.morse@arm.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=nd@arm.com \
--cc=oliver.upton@linux.dev \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=surenb@google.com \
--cc=will@kernel.org \
--cc=yeoreum.yun@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.