linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yeoreum Yun <yeoreum.yun@arm.com>
To: catalin.marinas@arm.com, will@kernel.org, broonie@kernel.org,
	anshuman.khandual@arm.com, joey.gouly@arm.com,
	yury.khrustalev@arm.com, maz@kernel.org, oliver.upton@linux.dev,
	frederic@kernel.org, shmeerali.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
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	nd@arm.com
Subject: Re: [PATCH v3 0/3] support FEAT_MTE_TAGGED_FAR feature
Date: Thu, 24 Apr 2025 14:49:48 +0100	[thread overview]
Message-ID: <aApBfHXRxn75Lebp@e129823.arm.com> (raw)
In-Reply-To: <20250410074721.947380-1-yeoreum.yun@arm.com>

Gentle ping in case of forgotten

> The FEAT_MTE_TAGGED_FAR feature provides support for
> reporting all non-address bits during a synchronous MTE tag check fault.
>
> This patchset extends the reporting tag to include
> not only the memory tag (logical tag) but also the address tag via
> si_addr when FEAT_MTE_TAGGED_FAR feature is supported.
>
> Since v1:
>   - add hwcap test for MTE_FAR feature.
>   - add MTE_FAR doc into elf_hwcap.rst
>
> Since v2:
>   - Rebase to 6.15-rc1
>
> Yeoreum Yun (3):
>   arm64: add FEAT_MTE_TAGGED_FAR feature
>   arm64/mm/fault: use original FAR_EL1 value when ARM64_MTE_FAR is
>     supported
>   tools/kselftest: add MTE_FAR hwcap test
>
>  Documentation/arch/arm64/elf_hwcaps.rst      |  3 +++
>  Documentation/arch/arm64/tagged-pointers.rst | 11 ++++++-----
>  arch/arm64/include/asm/hwcap.h               |  1 +
>  arch/arm64/include/uapi/asm/hwcap.h          |  1 +
>  arch/arm64/kernel/cpufeature.c               |  9 +++++++++
>  arch/arm64/kernel/cpuinfo.c                  |  1 +
>  arch/arm64/mm/fault.c                        |  7 +++++--
>  arch/arm64/tools/cpucaps                     |  1 +
>  tools/testing/selftests/arm64/abi/hwcap.c    |  6 ++++++
>  9 files changed, 33 insertions(+), 7 deletions(-)
>
> --
> LEVI:{C3F47F37-75D8-414A-A8BA-3980EC8A46D7}
>

--
Sincerely,
Yeoreum Yun

      parent reply	other threads:[~2025-04-24 13:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-10  7:47 [PATCH v3 0/3] support FEAT_MTE_TAGGED_FAR feature Yeoreum Yun
2025-04-10  7:47 ` [PATCH v3 1/3] arm64: add " Yeoreum Yun
2025-05-02 17:12   ` Catalin Marinas
2025-05-06 23:54     ` Yeoreum Yun
2025-04-10  7:47 ` [PATCH v3 2/3] arm64/mm/fault: use original FAR_EL1 value when ARM64_MTE_FAR is supported Yeoreum Yun
2025-05-02 17:08   ` Catalin Marinas
2025-05-02 18:25     ` Peter Collingbourne
2025-05-06 14:33       ` Yeoreum Yun
2025-04-10  7:47 ` [PATCH v3 3/3] tools/kselftest: add MTE_FAR hwcap test Yeoreum Yun
2025-05-02 17:15   ` Catalin Marinas
2025-05-06 23:56     ` Yeoreum Yun
2025-04-24 13:49 ` Yeoreum Yun [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=aApBfHXRxn75Lebp@e129823.arm.com \
    --to=yeoreum.yun@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=shmeerali.kolothum.thodi@huawei.com \
    --cc=surenb@google.com \
    --cc=will@kernel.org \
    --cc=yury.khrustalev@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;
as well as URLs for NNTP newsgroup(s).