From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v3 3/3] aarch64: Enhanced CPU diagnostics for ld.so
Date: Mon, 08 Apr 2024 10:38:10 +0200 [thread overview]
Message-ID: <877ch81c7h.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <946cbc29-07ea-4c2f-a65e-c67d4a0448c2@linaro.org> (Adhemerval Zanella Netto's message of "Fri, 5 Apr 2024 10:42:26 -0300")
* Adhemerval Zanella Netto:
> On 05/04/24 07:16, Florian Weimer wrote:
>> This prints some information from struct cpu_features, and the midr_el1
>> and dczid_el0 system register contents on every CPU.
>> ---
>> manual/dynlink.texi | 34 +++++++++++
>> sysdeps/aarch64/dl-diagnostics-cpu.c | 84 ++++++++++++++++++++++++++++
>> 2 files changed, 118 insertions(+)
>> create mode 100644 sysdeps/aarch64/dl-diagnostics-cpu.c
>>
>> diff --git a/manual/dynlink.texi b/manual/dynlink.texi
>> index f2f2341818..6f4acf321d 100644
>> --- a/manual/dynlink.texi
>> +++ b/manual/dynlink.texi
>> @@ -224,6 +224,40 @@ reflect adjustment by @theglibc{}.
>> These Linux-specific items show the values of @code{struct utsname}, as
>> reported by the @code{uname} function. @xref{Platform Type}.
>>
>> +@item aarch64.cpu_features.@dots{}
>> +These items are specific to the AArch64 architectures. They report data
>> +that is used by @theglibc{} to select alternative function
>> +implementations.
>
> Maybe also add some options are security related and not really tied
> to ifunc support (mte, bti).
I think MTE is also about selecting an implementation variant. I will
add something regarding BTI.
>> diff --git a/sysdeps/aarch64/dl-diagnostics-cpu.c b/sysdeps/aarch64/dl-diagnostics-cpu.c
>> new file mode 100644
>> index 0000000000..e037e6ea8c
>> --- /dev/null
>> +++ b/sysdeps/aarch64/dl-diagnostics-cpu.c
>> @@ -0,0 +1,84 @@
>> +/* Print CPU diagnostics data in ld.so. AArch64 version.
>> + Copyright (C) 2021-2024 Free Software Foundation, Inc.
>
> Maybe just 2024 here.
I started with a copy of the x86 file.
Thanks,
Florian
next prev parent reply other threads:[~2024-04-08 8:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 10:16 [PATCH v3 0/3] " Florian Weimer
2024-04-05 10:16 ` [PATCH v3 1/3] elf: Add CPU iteration support for future use in ld.so diagnostics Florian Weimer
2024-04-05 12:57 ` H.J. Lu
2024-04-05 10:16 ` [PATCH v3 2/3] x86: Add generic CPUID data dumper to ld.so --list-diagnostics Florian Weimer
2024-04-05 12:57 ` H.J. Lu
2024-04-05 10:16 ` [PATCH v3 3/3] aarch64: Enhanced CPU diagnostics for ld.so Florian Weimer
2024-04-05 13:42 ` Adhemerval Zanella Netto
2024-04-08 8:38 ` Florian Weimer [this message]
2024-04-05 14:49 ` Szabolcs Nagy
2024-04-05 14:54 ` Florian Weimer
2024-04-08 7:36 ` Szabolcs Nagy
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=877ch81c7h.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).