From: peterz@infradead.org
To: Feng Tang <feng.tang@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@intel.com>,
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 18:45:38 +0200 [thread overview]
Message-ID: <20200902164538.GN1362448@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1598514543-90152-1-git-send-email-feng.tang@intel.com>
On Thu, Aug 27, 2020 at 03:49:03PM +0800, Feng Tang wrote:
> End users frequently want to know what features their processor
> supports, independent of what the kernel supports.
>
> /proc/cpuinfo is great. It is omnipresent and since it is provided by
> the kernel it is always as up to date as the kernel. But, it can be
> ambiguous about processor features which can be disabled by the kernel
> at boot-time or compile-time.
Let me once again suggest we use CPUID faulting to 'fix' this.
We really should clear the CPUID bits when the kernel explicitly
disables things.
https://lkml.kernel.org/r/1552431636-31511-18-git-send-email-fenghua.yu@intel.com
next prev parent reply other threads:[~2020-09-02 16:45 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
2020-09-03 7:17 ` Feng Tang
2020-09-02 16:45 ` peterz [this message]
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=20200902164538.GN1362448@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=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=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).