From: "gaoliming" <gaoliming@byosoft.com.cn>
To: "'Ray Ni'" <ray.ni@intel.com>, <devel@edk2.groups.io>
Cc: "'Michael D Kinney'" <michael.d.kinney@intel.com>,
"'Zhiguang Liu'" <zhiguang.liu@intel.com>
Subject: 回复: [PATCH v3 2/4] MdePkg/Nasm.inc: add macros for C types used in structure definition
Date: Thu, 18 Feb 2021 11:24:35 +0800 [thread overview]
Message-ID: <000b01d705a5$9507fb70$bf17f250$@byosoft.com.cn> (raw)
In-Reply-To: <20210209141634.1999-3-ray.ni@intel.com>
Reviewed-by: Liming Gao <gaoliming@byosoft.com.cn>
> -----邮件原件-----
> 发件人: Ray Ni <ray.ni@intel.com>
> 发送时间: 2021年2月9日 22:17
> 收件人: devel@edk2.groups.io
> 抄送: Michael D Kinney <michael.d.kinney@intel.com>; Liming Gao
> <gaoliming@byosoft.com.cn>; Zhiguang Liu <zhiguang.liu@intel.com>
> 主题: [PATCH v3 2/4] MdePkg/Nasm.inc: add macros for C types used in
> structure definition
>
> Signed-off-by: Ray Ni <ray.ni@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>
> ---
> MdePkg/Include/Ia32/Nasm.inc | 38
> ++++++++++++++++++++++++++++++++++++
> MdePkg/Include/X64/Nasm.inc | 38
> ++++++++++++++++++++++++++++++++++++
> 2 files changed, 76 insertions(+)
>
> diff --git a/MdePkg/Include/Ia32/Nasm.inc
> b/MdePkg/Include/Ia32/Nasm.inc
> index 31ce861f1e..017fe5ffd8 100644
> --- a/MdePkg/Include/Ia32/Nasm.inc
> +++ b/MdePkg/Include/Ia32/Nasm.inc
> @@ -20,3 +20,41 @@
> %macro INCSSP_EAX 0
>
> DB 0xF3, 0x0F, 0xAE, 0xE8
>
> %endmacro
>
> +
>
> +; NASM provides built-in macros STRUC and ENDSTRUC for structure
> definition.
>
> +; For example, to define a structure called mytype containing a longword,
>
> +; a word, a byte and a string of bytes, you might code
>
> +;
>
> +; struc mytype
>
> +;
>
> +; mt_long: resd 1
>
> +; mt_word: resw 1
>
> +; mt_byte: resb 1
>
> +; mt_str: resb 32
>
> +;
>
> +; endstruc
>
> +;
>
> +; Below macros are help to map the C types and the RESB family of
> pseudo-instructions.
>
> +; So that the above structure definition can be coded as
>
> +;
>
> +; struc mytype
>
> +;
>
> +; mt_long: CTYPE_UINT32 1
>
> +; mt_word: CTYPE_UINT16 1
>
> +; mt_byte: CTYPE_UINT8 1
>
> +; mt_str: CTYPE_CHAR8 32
>
> +;
>
> +; endstruc
>
> +%define CTYPE_UINT64 resq
>
> +%define CTYPE_INT64 resq
>
> +%define CTYPE_UINT32 resd
>
> +%define CTYPE_INT32 resd
>
> +%define CTYPE_UINT16 resw
>
> +%define CTYPE_INT16 resw
>
> +%define CTYPE_BOOLEAN resb
>
> +%define CTYPE_UINT8 resb
>
> +%define CTYPE_CHAR8 resb
>
> +%define CTYPE_INT8 resb
>
> +
>
> +%define CTYPE_UINTN resd
>
> +%define CTYPE_INTN resd
>
> diff --git a/MdePkg/Include/X64/Nasm.inc b/MdePkg/Include/X64/Nasm.inc
> index 42412735ea..b48d8680bb 100644
> --- a/MdePkg/Include/X64/Nasm.inc
> +++ b/MdePkg/Include/X64/Nasm.inc
> @@ -20,3 +20,41 @@
> %macro INCSSP_RAX 0
>
> DB 0xF3, 0x48, 0x0F, 0xAE, 0xE8
>
> %endmacro
>
> +
>
> +; NASM provides built-in macros STRUC and ENDSTRUC for structure
> definition.
>
> +; For example, to define a structure called mytype containing a longword,
>
> +; a word, a byte and a string of bytes, you might code
>
> +;
>
> +; struc mytype
>
> +;
>
> +; mt_long: resd 1
>
> +; mt_word: resw 1
>
> +; mt_byte: resb 1
>
> +; mt_str: resb 32
>
> +;
>
> +; endstruc
>
> +;
>
> +; Below macros are help to map the C types and the RESB family of
> pseudo-instructions.
>
> +; So that the above structure definition can be coded as
>
> +;
>
> +; struc mytype
>
> +;
>
> +; mt_long: CTYPE_UINT32 1
>
> +; mt_word: CTYPE_UINT16 1
>
> +; mt_byte: CTYPE_UINT8 1
>
> +; mt_str: CTYPE_CHAR8 32
>
> +;
>
> +; endstruc
>
> +%define CTYPE_UINT64 resq
>
> +%define CTYPE_INT64 resq
>
> +%define CTYPE_UINT32 resd
>
> +%define CTYPE_INT32 resd
>
> +%define CTYPE_UINT16 resw
>
> +%define CTYPE_INT16 resw
>
> +%define CTYPE_BOOLEAN resb
>
> +%define CTYPE_UINT8 resb
>
> +%define CTYPE_CHAR8 resb
>
> +%define CTYPE_INT8 resb
>
> +
>
> +%define CTYPE_UINTN resq
>
> +%define CTYPE_INTN resq
>
> --
> 2.27.0.windows.1
next prev parent reply other threads:[~2021-02-18 3:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 14:16 [PATCH v3 0/4] Use XADD to avoid lock acquire/release Ni, Ray
2021-02-09 14:16 ` [PATCH v3 1/4] UefiCpuPkg/MpInitLib: " Ni, Ray
2021-02-22 9:06 ` Dong, Eric
2021-02-23 18:11 ` [edk2-devel] " Michael D Kinney
2021-02-25 4:04 ` Ni, Ray
2021-02-25 19:02 ` Laszlo Ersek
2021-02-09 14:16 ` [PATCH v3 2/4] MdePkg/Nasm.inc: add macros for C types used in structure definition Ni, Ray
2021-02-18 3:24 ` gaoliming [this message]
2021-02-09 14:16 ` [PATCH v3 3/4] UefiCpuPkg/MpInitLib: Use NASM struc to avoid hardcode offset Ni, Ray
2021-02-22 9:06 ` Dong, Eric
2021-02-09 14:16 ` [PATCH v3 4/4] UefiCpuPkg/MpInitLib: Remove unused Lock from MP_CPU_EXCHANGE_INFO Ni, Ray
2021-02-22 9:07 ` Dong, Eric
[not found] ` <166219FF4C25D9C5.16853@groups.io>
2021-02-23 2:22 ` [edk2-devel] [PATCH v3 1/4] UefiCpuPkg/MpInitLib: Use XADD to avoid lock acquire/release Ni, Ray
2021-02-25 19:03 ` [edk2-devel] [PATCH v3 0/4] " Laszlo Ersek
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='000b01d705a5$9507fb70$bf17f250$@byosoft.com.cn' \
--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