public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Noah Goldstein <goldstein.w.n@gmail.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 2/2] x86: Add generic CPUID data dumper to ld.so --list-diagnostics
Date: Mon, 11 Sep 2023 19:48:35 +0200	[thread overview]
Message-ID: <87bke8ppn0.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAFUsyfKyS3FA=m-dRY3o3d=oPc-e5=9zPDrCM72ou=4K4uk91Q@mail.gmail.com> (Noah Goldstein's message of "Mon, 11 Sep 2023 11:28:54 -0500")

* Noah Goldstein:

>> > If JSON isn't really feasible for technical reasons, however, so be it.
>>
>> There is that 53 bit problem, and we'd still have to use string keys for
>> the objects.
>
> We can't find meaningful names for the information? If not do we even
> want to dump it?

My goal was to write a generic dumper, not something we need update for
every new CPU generation.  That's why I didn't want to hard-code subleaf
structure and implement a brute-force approach instead.

For example, when we had the leaf 2 problems, the existing dumps were
insufficient.  Tomorrow it might be a completely different leaf.  And
the dumper intends to cover everything, including parts that are only
used by (possibly future) GCC versions in __builtin_cpu_supports.

Thanks,
Florian


  parent reply	other threads:[~2023-09-11 17:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08 20:09 [PATCH 1/2] elf: Wire up _dl_diagnostics_cpu_kernel Florian Weimer
2023-09-08 20:10 ` [PATCH 2/2] x86: Add generic CPUID data dumper to ld.so --list-diagnostics Florian Weimer
2023-09-10 19:56   ` Noah Goldstein
2023-09-11  4:24     ` Florian Weimer
2023-09-11 16:16       ` Noah Goldstein
2023-09-11 16:25         ` Florian Weimer
2023-09-11 16:28           ` Noah Goldstein
2023-09-11 16:31             ` Noah Goldstein
2023-09-11 17:48             ` Florian Weimer [this message]
2023-09-11 18:35               ` Noah Goldstein
2023-09-11 16:08   ` Adhemerval Zanella Netto
2023-09-11 16:19     ` Florian Weimer
2023-09-11 16:41       ` Adhemerval Zanella Netto
2024-02-09 19:08 [PATCH 0/2] Enhanced x86 CPU diagnostics Florian Weimer
2024-02-09 19:08 ` [PATCH 2/2] x86: Add generic CPUID data dumper to ld.so --list-diagnostics Florian Weimer
2024-02-09 19:34   ` H.J. Lu
2024-02-10  0:44     ` H.J. Lu

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=87bke8ppn0.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=goldstein.w.n@gmail.com \
    --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).