From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: Joey Vagedes <joey.vagedes@gmail.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Gao, Liming" <gaoliming@byosoft.com.cn>,
"Liu, Zhiguang" <zhiguang.liu@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [PATCH v1 1/2] MdePkg: IndustryStandard: Add DLL Characteristics
Date: Tue, 27 Jun 2023 20:12:21 +0000 [thread overview]
Message-ID: <SA2PR11MB4938F876375EE1050B2197DED227A@SA2PR11MB4938.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230623154442.799-2-joey.vagedes@gmail.com>
Hi Joey,
Was the link to the PE/COFF specs that added these updated in the file header?
Also, shouldn't it be DLL_CHARACTERISRICS instead of DLLCHARACTERISRICS?
Mike
> -----Original Message-----
> From: Joey Vagedes <joey.vagedes@gmail.com>
> Sent: Friday, June 23, 2023 8:45 AM
> To: devel@edk2.groups.io
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Gao, Liming
> <gaoliming@byosoft.com.cn>; Liu, Zhiguang <zhiguang.liu@intel.com>
> Subject: [PATCH v1 1/2] MdePkg: IndustryStandard: Add DLL Characteristics
>
> Add the bit masks for DLL Characteristics, used within the optional
> header of a PE, to the PeImage.h header file.
>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
> Cc: Zhiguang Liu <zhiguang.liu@intel.com>
> Signed-off-by: Joey Vagedes <joeyvagedes@gmail.com>
> ---
> MdePkg/Include/IndustryStandard/PeImage.h | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/MdePkg/Include/IndustryStandard/PeImage.h
> b/MdePkg/Include/IndustryStandard/PeImage.h
> index 47037049348c..430e8988f550 100644
> --- a/MdePkg/Include/IndustryStandard/PeImage.h
> +++ b/MdePkg/Include/IndustryStandard/PeImage.h
> @@ -269,6 +269,21 @@ typedef struct {
> #define EFI_IMAGE_SUBSYSTEM_OS2_CUI 5
> #define EFI_IMAGE_SUBSYSTEM_POSIX_CUI 7
>
> +//
> +// DLL Characteristics
> +//
> +#define IMAGE_DLLCHARACTERISTICS_HIGH_ENTROPY_VA 0x0020
> +#define IMAGE_DLLCHARACTERISTICS_DYNAMIC_BASE 0x0040
> +#define IMAGE_DLLCHARACTERISTICS_FORCE_INTEGRITY 0x0080
> +#define IMAGE_DLLCHARACTERISTICS_NX_COMPAT 0x0100
> +#define IMAGE_DLLCHARACTERISTICS_NO_ISOLATION 0x0200
> +#define IMAGE_DLLCHARACTERISTICS_NO_SEH 0x0400
> +#define IMAGE_DLLCHARACTERISTICS_NO_BIND 0x0800
> +#define IMAGE_DLLCHARACTERISTICS_APPCONTAINER 0x1000
> +#define IMAGE_DLLCHARACTERISTICS_WDM_DRIVER 0x2000
> +#define IMAGE_DLLCHARACTERISTICS_GUARD_CF 0x4000
> +#define IMAGE_DLLCHARACTERISTICS_TERMINAL_SERVER_AWARE 0x8000
> +
> ///
> /// Length of ShortName.
> ///
> --
> 2.41.0.windows.1
next prev parent reply other threads:[~2023-06-27 20:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 15:44 [PATCH v1 0/2] Automatically set NXCOMPAT bit if requirements are met Joey Vagedes
2023-06-23 15:44 ` [PATCH v1 1/2] MdePkg: IndustryStandard: Add DLL Characteristics Joey Vagedes
2023-06-27 20:12 ` Michael D Kinney [this message]
2023-06-27 21:42 ` Joey Vagedes
2023-06-27 23:51 ` Michael D Kinney
2023-06-23 15:44 ` [PATCH v1 2/2] BaseTools: GenFw: auto-set nxcompat flag Joey Vagedes
2023-07-06 15:26 ` Joey Vagedes
2023-07-09 23:24 ` Rebecca Cran
2023-06-23 16:11 ` [edk2-devel] [PATCH v1 0/2] Automatically set NXCOMPAT bit if requirements are met Ard Biesheuvel
2023-06-27 22:23 ` Joey Vagedes
2023-06-25 2:44 ` 回复: " gaoliming
2023-06-26 21:58 ` Joey Vagedes
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=SA2PR11MB4938F876375EE1050B2197DED227A@SA2PR11MB4938.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