From: Terry Bowman <terry.bowman@amd.com>
To: <terry.bowman@amd.com>, <linux-kernel@vger.kernel.org>,
<bp@suse.de>, <feng.tang@intel.com>, <x86@kernel.org>
Subject: [PATCH 0/3] Update kcpuid leaves and tool
Date: Mon, 6 Feb 2023 08:18:29 -0600 [thread overview]
Message-ID: <20230206141832.4162264-1-terry.bowman@amd.com> (raw)
The 1st patch fixes incorrect bit offsets for Fn00000007_EBX features
avx512bw and avx512lvl.
The 2nd patch adds missing features to leaf Fn80000001.
The 3rd patch updates details displayed by kcpuid tool.
Base is 63fce5464aa5.
Borislav Petkov (AMD) (1):
tools/x86/kcpuid: Dump the CPUID function in detailed view
Terry Bowman (2):
tools/x86/kcpuid: Fix avx512bw and avx512lvl fields in Fn00000007
tools/x86/kcpuid: Update AMD leaf Fn80000001
tools/arch/x86/kcpuid/cpuid.csv | 61 ++++++++++++++++++++++++++++++---
tools/arch/x86/kcpuid/kcpuid.c | 10 +++++-
2 files changed, 65 insertions(+), 6 deletions(-)
--
2.34.1
next reply other threads:[~2023-02-06 14:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 14:18 Terry Bowman [this message]
2023-02-06 14:18 ` [PATCH 1/3] tools/x86/kcpuid: Fix avx512bw and avx512lvl fields in Fn00000007 Terry Bowman
2023-02-07 3:28 ` Feng Tang
2023-03-07 22:41 ` [tip: x86/misc] " tip-bot2 for Terry Bowman
2023-02-06 14:18 ` [PATCH 2/3] tools/x86/kcpuid: Update AMD leaf Fn80000001 Terry Bowman
2023-02-07 3:49 ` Feng Tang
2023-02-07 15:47 ` Borislav Petkov
2023-02-08 6:15 ` Feng Tang
2023-03-07 22:41 ` [tip: x86/misc] " tip-bot2 for Terry Bowman
2023-02-06 14:18 ` [PATCH 3/3] tools/x86/kcpuid: Dump the CPUID function in detailed view Terry Bowman
2023-02-07 3:42 ` Feng Tang
2023-02-07 16:17 ` Borislav Petkov
2023-02-08 6:13 ` Feng Tang
2023-03-07 22:41 ` [tip: x86/misc] " tip-bot2 for Borislav Petkov (AMD)
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=20230206141832.4162264-1-terry.bowman@amd.com \
--to=terry.bowman@amd.com \
--cc=bp@suse.de \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®