From: "Ahmed S. Darwish" <darwi@linutronix.de>
To: Tony W Wang-oc <TonyWWang-oc@zhaoxin.com>, x86-cpuid@lists.linux.dev
Cc: terry.bowman@amd.com, bp@alien8.de, feng.tang@intel.com,
linux-kernel@vger.kernel.org, CobeChen@zhaoxin.com,
TimGuo@zhaoxin.com, LeoLiu-oc@zhaoxin.com
Subject: Re: [PATCH] tools/x86/kcpuid: Add extended CPUID leaf 0xc0000001 support
Date: Wed, 9 Oct 2024 13:22:44 +0200 [thread overview]
Message-ID: <ZwZnhGfSPHTz64dm@lx-t490> (raw)
In-Reply-To: <20230530025922.4801-1-TonyWWang-oc@zhaoxin.com>
Hi Tony,
On Tue, 30 May 2023, Tony W Wang-oc wrote:
>
> CPUID leaf 0xc0000001 EDX bit2/3/6-13 are used by VIA/Cyrix/
> Centaur to defined CPU features.
>
> Zhaoxin use CPUID leaf 0xc0000001 EDX as:
> CPUID.(EAX=0xc0000001,ECX=0):EDX[bit 0] SM2
> CPUID.(EAX=0xc0000001,ECX=0):EDX[bit 1] SM2_EN
> CPUID.(EAX=0xc0000001,ECX=0):EDX[bit 4] SM3 SM4
> CPUID.(EAX=0xc0000001,ECX=0):EDX[bit 5] SM3_EN SM4_EN
> CPUID.(EAX=0xc0000001,ECX=0):EDX[bit 16] PARALLAX
> CPUID.(EAX=0xc0000001,ECX=0):EDX[bit 17] PARALLAX_EN
> CPUID.(EAX=0xc0000001,ECX=0):EDX[bit 20] TM3
> CPUID.(EAX=0xc0000001,ECX=0):EDX[bit 21] TM3_EN
> CPUID.(EAX=0xc0000001,ECX=0):EDX[bit 22] RNG2
> CPUID.(EAX=0xc0000001,ECX=0):EDX[bit 23] RNG2_EN
> CPUID.(EAX=0xc0000001,ECX=0):EDX[bit 25] PHE2
> CPUID.(EAX=0xc0000001,ECX=0):EDX[bit 26] PHE2_EN
> CPUID.(EAX=0xc0000001,ECX=0):EDX[bit 27] RSA
> CPUID.(EAX=0xc0000001,ECX=0):EDX[bit 28] RSA_EN
>
Just a short note. I've added these bits to the x86-cpuid-db database:
https://gitlab.com/x86-cpuid.org/x86-cpuid-db/-/blob/tip/db/xml/leaf_c0000001.xml
And they're now part of the project's v2.0 release:
https://lore.kernel.org/x86-cpuid/ZwU0HtmCTj2rF2T8@lx-t490
I shall send a kcpuid PQ with the updated CSV at a later step.
Thanks,
--
Ahmed S. Darwish
Linutronix GmbH
prev parent reply other threads:[~2024-10-09 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 2:59 [PATCH] tools/x86/kcpuid: Add extended CPUID leaf 0xc0000001 support Tony W Wang-oc
2024-10-09 11:22 ` Ahmed S. Darwish [this message]
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=ZwZnhGfSPHTz64dm@lx-t490 \
--to=darwi@linutronix.de \
--cc=CobeChen@zhaoxin.com \
--cc=LeoLiu-oc@zhaoxin.com \
--cc=TimGuo@zhaoxin.com \
--cc=TonyWWang-oc@zhaoxin.com \
--cc=bp@alien8.de \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=terry.bowman@amd.com \
--cc=x86-cpuid@lists.linux.dev \
/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