From: Borislav Petkov <bp@alien8.de>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Feng Tang <feng.tang@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] tools/x86: add kcpuid tool to show raw CPU features
Date: Wed, 2 Sep 2020 20:19:56 +0200 [thread overview]
Message-ID: <20200902181956.GD21537@zn.tnic> (raw)
In-Reply-To: <98adc930-00e2-67c8-4ba3-fcb1af3aafd2@intel.com>
On Wed, Sep 02, 2020 at 10:18:38AM -0700, Dave Hansen wrote:
> All good points.
>
> Personally, I think I'd be OK if kcpuid _focused_ on single-bit values
> only. Those are the vast majority of the things that we need from such
> a tool. I don't think there's nearly as much demand for the topology
> enumeration or TLB structure leaf parsing.
>
> I also kinda doubt we can come up with a file format off the top of our
> heads that can represent all the ways data is represented in the CPUID
> space. Single bits, sure.
Yap, agreed.
However, we should try to at least provide for some rudimentary support
for multibit fields in case we decide we need them down the road and
after the fact.
I guess it is enough if the tool dumps them and their meaning - if one
needs further info then one would go do the *actual* CPU documentation
anyway...
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-09-02 18:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 7:49 [RFC PATCH] tools/x86: add kcpuid tool to show raw CPU features Feng Tang
2020-09-02 15:40 ` Borislav Petkov
2020-09-02 16:25 ` Dave Hansen
2020-09-02 16:52 ` Borislav Petkov
2020-09-02 17:18 ` Dave Hansen
2020-09-02 18:19 ` Borislav Petkov [this message]
2020-09-03 7:17 ` Feng Tang
2020-09-02 16:45 ` peterz
2020-09-02 16:52 ` Dave Hansen
2020-09-02 16:59 ` peterz
2020-09-02 16:55 ` Borislav Petkov
2020-09-02 17:01 ` peterz
-- strict thread matches above, loose matches on Subject: below --
2020-07-21 2:00 Feng Tang
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=20200902181956.GD21537@zn.tnic \
--to=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=feng.tang@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 NNTP newsgroup(s).