From: "Ni, Ray" <ray.ni@intel.com>
To: "Lou, Yun" <yun.lou@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
"Liu, Zhiguang" <zhiguang.liu@intel.com>
Subject: Re: [PATCH v3] MdePkg/Cpuid.h: Define new element in CPUID Leaf(07h) data structure.
Date: Fri, 9 Apr 2021 01:16:11 +0000 [thread overview]
Message-ID: <CO1PR11MB49306BDCBBB854BDF9761B968C739@CO1PR11MB4930.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210408145049.14851-1-yun.lou@intel.com>
Jason,
Reserved3 doesn't need to change because its position and width are not changed.
> -----Original Message-----
> From: Lou, Yun <yun.lou@intel.com>
> Sent: Thursday, April 8, 2021 10:51 PM
> To: devel@edk2.groups.io
> Cc: Lou, Yun <yun.lou@intel.com>; Kinney, Michael D <michael.d.kinney@intel.com>; Liming Gao <gaoliming@byosoft.com.cn>;
> Liu, Zhiguang <zhiguang.liu@intel.com>; Ni, Ray <ray.ni@intel.com>
> Subject: [PATCH v3] MdePkg/Cpuid.h: Define new element in CPUID Leaf(07h) data structure.
>
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3309
>
> Define new element(Hybird) in CPUID_STRUCTURED_EXTENDED_FEATURE_FLAGS
> (07h) data structure.
>
> Signed-off-by: Jason Lou <yun.lou@intel.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
> Cc: Zhiguang Liu <zhiguang.liu@intel.com>
> Cc: Ray Ni <ray.ni@intel.com>
> ---
> MdePkg/Include/Register/Intel/Cpuid.h | 16 ++++++++++++----
> 1 file changed, 12 insertions(+), 4 deletions(-)
>
> diff --git a/MdePkg/Include/Register/Intel/Cpuid.h b/MdePkg/Include/Register/Intel/Cpuid.h
> index 19af99b6af..25ec65a746 100644
> --- a/MdePkg/Include/Register/Intel/Cpuid.h
> +++ b/MdePkg/Include/Register/Intel/Cpuid.h
> @@ -6,7 +6,7 @@
> If a register returned is a single 32-bit value, then a data structure is
>
> not provided for that register.
>
>
>
> - Copyright (c) 2015 - 2019, Intel Corporation. All rights reserved.<BR>
>
> + Copyright (c) 2015 - 2021, Intel Corporation. All rights reserved.<BR>
>
> SPDX-License-Identifier: BSD-2-Clause-Patent
>
>
>
> @par Specification Reference:
>
> @@ -1550,9 +1550,17 @@ typedef union {
> ///
>
> UINT32 AVX512_4FMAPS:1;
>
> ///
>
> - /// [Bit 25:4] Reserved.
>
> + /// [Bit 14:4] Reserved.
>
> ///
>
> - UINT32 Reserved2:22;
>
> + UINT32 Reserved4:11;
>
> + ///
>
> + /// [Bit 15] Hybrid. If 1, the processor is identified as a hybrid part.
>
> + ///
>
> + UINT32 Hybrid:1;
>
> + ///
>
> + /// [Bit 25:16] Reserved.
>
> + ///
>
> + UINT32 Reserved5:10;
>
> ///
>
> /// [Bit 26] Enumerates support for indirect branch restricted speculation
>
> /// (IBRS) and the indirect branch pre-dictor barrier (IBPB). Processors
>
> @@ -1581,7 +1589,7 @@ typedef union {
> ///
>
> /// [Bit 30] Reserved.
>
> ///
>
> - UINT32 Reserved3:1;
>
> + UINT32 Reserved6:1;
>
> ///
>
> /// [Bit 31] Enumerates support for Speculative Store Bypass Disable (SSBD).
>
> /// Processors that set this bit sup-port the IA32_SPEC_CTRL MSR. They allow
>
> --
> 2.28.0.windows.1
next prev parent reply other threads:[~2021-04-09 1:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 14:50 [PATCH v3] MdePkg/Cpuid.h: Define new element in CPUID Leaf(07h) data structure Jason Lou
2021-04-09 1:16 ` Ni, Ray [this message]
2021-04-09 1:58 ` [edk2-devel] " Jason Lou
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=CO1PR11MB49306BDCBBB854BDF9761B968C739@CO1PR11MB4930.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