lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aEmBprs3ivyhJdek@e129823.arm.com>
Date: Wed, 11 Jun 2025 14:16:22 +0100
From: Yeoreum Yun <yeoreum.yun@....com>
To: Mark Brown <broonie@...nel.org>
Cc: Catalin Marinas <Catalin.Marinas@....com>,
	"pcc@...gle.com" <pcc@...gle.com>,
	"will@...nel.org" <will@...nel.org>,
	Anshuman Khandual <Anshuman.Khandual@....com>,
	Joey Gouly <Joey.Gouly@....com>,
	Yury Khrustalev <Yury.Khrustalev@....com>,
	"maz@...nel.org" <maz@...nel.org>,
	"oliver.upton@...ux.dev" <oliver.upton@...ux.dev>,
	"frederic@...nel.org" <frederic@...nel.org>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"surenb@...gle.com" <surenb@...gle.com>,
	"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>
Subject: Re: [PATCH v6 2/9] arm64: report address tag when
 FEAT_MTE_TAGGED_FAR is supported

Hi Mark,

> >
> > > > +HWCAP3_MTE_FAR
> > >
> > > > +��� Functionality implied by ID_AA64PFR2_EL1.MTEFAR == 0b0001.
> > > > +Applications should interpret the values of these bits based on
> > > > +the support for the 'mte_far' hwcap. If the support is not present,
> > > > +the values of these bits should be considered as undefined otherwise valid.
> > >
> > > The constant is HWCAP3_MTE_FAR and the cpuinfo is mtefar:
> > >
> > > +���� [KERNEL_HWCAP_MTE_FAR]��������� = "mtefar",
> > >
> > > The reference to the hwcap should probably be one of these, I'd go for
> > > HWCAP3_MTE_FAR since it says hwcap.
>
> > Just for confirmation. so change to "mtefar" -> "mte_far"
> > Am I missing?
>
> I'd write it as HWCAP3_MTE_FAR since that's the thing you're
> referencing.

Ah I see for documents. Thanks!


--
Sincerely,
Yeoreum Yun

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ