From: "Ni, Ray" <ray.ni@intel.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
"Liu, Zhiguang" <zhiguang.liu@intel.com>,
"Dong, Eric" <eric.dong@intel.com>,
"Kumar, Rahul R" <rahul.r.kumar@intel.com>,
Gerd Hoffmann <kraxel@redhat.com>,
"Ard Biesheuvel" <ardb+tianocore@kernel.org>
Cc: Michael Roth <michael.roth@amd.com>
Subject: Re: [edk2-devel] [PATCH 1/2] UefiCpuPkg/MpInitLib: Use AsmCpuidEx() for CPUID_EXTENDED_TOPOLOGY leaf
Date: Sun, 21 Jan 2024 03:00:04 +0000 [thread overview]
Message-ID: <MN6PR11MB82446E03245943152098B5508C762@MN6PR11MB8244.namprd11.prod.outlook.com> (raw)
In-Reply-To: <72123232-5a27-7778-591d-69fc7fda0881@amd.com>
> The worry I have here is that it becomes a maintenance concern having to
> update the list of leaves with sub-leaves whenever a new CPUID leaf with
> sub-leaves is introduced.
Intel SDM or AMD equivalent "SDM" should not change a CPUID leaf in a way
that it does not consume ECX today but consume it tomorrow.
This is a non-backward compatible instruction change.
With that, it's easy to maintain a list of CPUID leaf that does not have sub-leaf
today, or a list of ones that have sub-leaf.
It's a feature to help on debuggability, similar to today's StrLen() implementation
in BaseLib that avoids reading the memory to no-end.
>
> >
> > Another concern I have if AsmCpuid() zeros ECX is callers would call
> AsmCpuid(leaf) instead of AsmCpuidEx (leaf, 0).
> > This would cause the caller code a mess.
>
> I think it's just a mindset that I have from kernel programming. In Linux,
> the AsmCpuid() equivalent will explicitly zero the ECX register so that
> you get the zero sub-leaf if that leaf has sub-leaves.
>
> Using AsmCpuid() where ECX is non-zero and possibly random, could make
> debugging harder. By zeroing ECX, you will get repeatable return values to
> help with debugging when things aren't going right.
I agree with your concern.
How about having both? I mean not only zeroing out ECX but also rejecting the
CPUID leaves which have sub-leaf.
It's a lib API. I still don't want AsmCpuid to own the responsibility to call sub-leaf 0.
So, in debug build, AsmCpuid() asserts on some calls.
In release build, we get fixed behavior.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#114122): https://edk2.groups.io/g/devel/message/114122
Mute This Topic: https://groups.io/mt/102432782/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-01-21 3:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 22:45 [edk2-devel] [PATCH 0/2] SEV-SNP guest support fixes Lendacky, Thomas via groups.io
2023-11-06 22:45 ` [edk2-devel] [PATCH 1/2] UefiCpuPkg/MpInitLib: Use AsmCpuidEx() for CPUID_EXTENDED_TOPOLOGY leaf Lendacky, Thomas via groups.io
2023-11-28 10:31 ` Ni, Ray
2023-11-06 22:45 ` [edk2-devel] [PATCH 2/2] UefiCpuPkg/MpInitLib: Copy SEV-ES save area pointer during APIC ID sorting Lendacky, Thomas via groups.io
2023-11-28 10:33 ` Ni, Ray
[not found] ` <17952A20A9E21541.12603@groups.io>
2023-11-06 23:15 ` [edk2-devel] [PATCH 1/2] UefiCpuPkg/MpInitLib: Use AsmCpuidEx() for CPUID_EXTENDED_TOPOLOGY leaf Lendacky, Thomas via groups.io
2023-11-07 1:19 ` Michael D Kinney
2023-11-28 14:35 ` Lendacky, Thomas via groups.io
[not found] ` <179BD02AA4207037.22216@groups.io>
2024-01-17 21:26 ` Lendacky, Thomas via groups.io
2024-01-18 23:10 ` Michael D Kinney
2024-01-19 10:00 ` Ni, Ray
2024-01-19 23:16 ` Michael D Kinney
2024-01-19 23:48 ` Ni, Ray
2024-01-20 1:49 ` Michael D Kinney
2024-01-20 6:48 ` Ni, Ray
2024-01-20 16:03 ` Lendacky, Thomas via groups.io
2024-01-21 3:00 ` Ni, Ray [this message]
2023-11-07 9:55 ` [edk2-devel] [PATCH 0/2] SEV-SNP guest support fixes Gerd Hoffmann
2023-11-17 21:43 ` Lendacky, Thomas via groups.io
2023-11-27 19:00 ` Lendacky, Thomas via groups.io
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-list 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=MN6PR11MB82446E03245943152098B5508C762@MN6PR11MB8244.namprd11.prod.outlook.com \
--to=devel@edk2.groups.io \
/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