public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, ray.ni@intel.com
Cc: Michael D Kinney <michael.d.kinney@intel.com>,
	Liming Gao <gaoliming@byosoft.com.cn>,
	Zhiguang Liu <zhiguang.liu@intel.com>
Subject: Re: [edk2-devel] [PATCH v2 1/3] MdePkg/Nasm.inc: add macros for C types used in structure definition
Date: Fri, 5 Feb 2021 16:02:54 +0100	[thread overview]
Message-ID: <3d1e6971-20b5-33fd-dc96-1a058d802b13@redhat.com> (raw)
In-Reply-To: <20210205075810.981-2-ray.ni@intel.com>

On 02/05/21 08:58, Ni, Ray wrote:
> 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
> 

Reviewed-by: Laszlo Ersek <lersek@redhat.com>


  reply	other threads:[~2021-02-05 15:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05  7:58 [PATCH v2 0/3] Use XADD to avoid lock acquire/release Ni, Ray
2021-02-05  7:58 ` [PATCH v2 1/3] MdePkg/Nasm.inc: add macros for C types used in structure definition Ni, Ray
2021-02-05 15:02   ` Laszlo Ersek [this message]
2021-02-05  7:58 ` [PATCH v2 2/3] UefiCpuPkg/MpInitLib: Use NASM struc to avoid hardcode offset Ni, Ray
2021-02-05 15:09   ` [edk2-devel] " Laszlo Ersek
2021-02-05  7:58 ` [PATCH v2 3/3] UefiCpuPkg/MpInitLib: Use XADD to avoid lock acquire/release Ni, Ray
2021-02-05 15:11   ` [edk2-devel] " Laszlo Ersek
2021-02-05 17:11 ` [edk2-devel] [PATCH v2 0/3] " Michael D Kinney
2021-02-05 18:38   ` Ni, Ray
2021-02-05 19:54     ` Michael D Kinney
2021-02-06  4:32       ` Ni, Ray

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=3d1e6971-20b5-33fd-dc96-1a058d802b13@redhat.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