[PATCH v7 18/23] aarch64: Handle GCS marking
Yury Khrustalev
yury.khrustalev@arm.com
Wed Jan 8 14:20:37 GMT 2025
On Wed, Jan 08, 2025 at 11:08:07AM -0300, Adhemerval Zanella Netto wrote:
>
> >> This requires to update the glibc.cpu.aarch64_gcs_policy entry at
> >> manual/tunables.texi with the description of what each value represents.
> >
> > Right now GCS tunable names are reserved in the manual. When corresponding
> > Linux kernel functionality has been released, there will be another patch
> > for Glibc that will add the description of both GCS tunables. At this point
> > these tunables will become "public". This will likely be after the upcoming
> > Glibc release.
>
> Ok, but this code is already defining the logic of how aarch64_gcs_policy
> works and when a user glibc on a GCS enabled kernel the tunable will be
> enacted. I still think we need to document the current semantic, the
> reserved rationale would make sense if the tunable was not enacted.
Carlos, can I ask for your opinion? I thought we discussed this and the decision
was to reserve tunable names for now and document them properly later after the
corresponding Linux kernel functionality has been released.
Thanks,
Yury
More information about the Libc-alpha
mailing list