From: Yeoreum Yun <yeoreum.yun@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: catalin.marinas@arm.com, pcc@google.com, will@kernel.org,
anshuman.khandual@arm.com, joey.gouly@arm.com,
yury.khrustalev@arm.com, maz@kernel.org, oliver.upton@linux.dev,
frederic@kernel.org, akpm@linux-foundation.org,
surenb@google.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v7 2/9] arm64: report address tag when FEAT_MTE_TAGGED_FAR is supported
Date: Wed, 11 Jun 2025 18:59:05 +0100 [thread overview]
Message-ID: <aEnD6VOsz8zlQA/7@e129823.arm.com> (raw)
In-Reply-To: <d93452bf-7296-47fc-9d48-44c390cb5080@sirena.org.uk>
Hi Mark,
> > > On Wed, Jun 11, 2025 at 02:58:11PM +0100, Yeoreum Yun wrote:
>
> > > > * The architecture specifies that bits 63:60 of FAR_EL1 are UNKNOWN
> > > > * for tag check faults. Set them to corresponding bits in the untagged
> > > > - * address.
> > > > + * address if ARM64_MTE_FAR isn't supported.
> > > > + * Otherwise, bits 63:60 of FAR_EL1 are KNOWN.
>
> > > Should that be "are UNKNOWN"?
>
> > Otherwise in here mentions the case when ARM64_MTE_FAR is supported,
> > So the bits 63:60 of FAR_EL1 are "not UNKNOWN" but I write it with
> > KNOWN.
>
> Ah, I see - KNOWN looks like one of the specially defined architectural
> terms from the glossary of the ARM since it's all caps but KNOWN isn't
> one of those words which was confusing me.
>
> > Do you want to change this to "not UNKNOWN"?
> > or Am I missing something?
>
> DDI0487L.a D24.2.43 does use the term "not UNKNOWN" for that case so
> that'd work like you suggest, or some other rewrite to use less formal
> terms. Like I say it was specifically the use of caps.
Sorry to make you confused. anyway I'll use the term with not UNKNOWN
then.
Thanks
--
Sincerely,
Yeoreum Yun
next prev parent reply other threads:[~2025-06-11 17:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 13:58 [PATCH v7 0/9] support FEAT_MTE_TAGGED_FAR feature Yeoreum Yun
2025-06-11 13:58 ` [PATCH v7 1/9] arm64/cpufeature: add " Yeoreum Yun
2025-06-12 7:36 ` Marc Zyngier
2025-06-17 18:38 ` Yeoreum Yun
2025-06-11 13:58 ` [PATCH v7 2/9] arm64: report address tag when FEAT_MTE_TAGGED_FAR is supported Yeoreum Yun
2025-06-11 15:14 ` Mark Brown
2025-06-11 15:29 ` Yeoreum Yun
2025-06-11 16:17 ` Mark Brown
2025-06-11 17:59 ` Yeoreum Yun [this message]
2025-06-11 13:58 ` [PATCH v7 3/9] tools/kselftest: add MTE_FAR hwcap test Yeoreum Yun
2025-06-11 13:58 ` [PATCH v7 4/9] kselftest/arm64/mte: register mte signal handler with SA_EXPOSE_TAGBITS Yeoreum Yun
2025-06-11 13:58 ` [PATCH v7 5/9] kselftest/arm64/mte: check MTE_FAR feature is supported Yeoreum Yun
2025-06-11 15:20 ` Mark Brown
2025-06-11 13:58 ` [PATCH v7 6/9] kselftest/arm64/mte: add address tag related macro and function Yeoreum Yun
2025-06-11 15:21 ` Mark Brown
2025-06-11 13:58 ` [PATCH v7 7/9] kselftest/arm64/mte: add verification for address tag in signal handler Yeoreum Yun
2025-06-11 13:58 ` [PATCH v7 8/9] kselftest/arm64/mte: refactor check_mmap_option test Yeoreum Yun
2025-06-11 13:58 ` [PATCH v7 9/9] kselftest/arm64/mte: add mtefar tests on check_mmap_options Yeoreum Yun
2025-06-11 15:29 ` 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=aEnD6VOsz8zlQA/7@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=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pcc@google.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).