public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Liming Gao" <liming.gao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Gao, Liming" <liming.gao@intel.com>,
	"Huang, Qing" <qing.huang@intel.com>
Subject: Re: [edk2-devel] [PATCH] MdePkg-UefiSpec.h: Add UEFI 2.8 new memory attributes
Date: Mon, 4 Nov 2019 02:08:55 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E536943@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <15D256836EC4F298.17962@groups.io>

Push @ c18708d2f002a6ea43ed65d6c76dc4020687005c

>-----Original Message-----
>From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
>Liming Gao
>Sent: Wednesday, October 30, 2019 1:46 PM
>To: Huang, Qing <qing.huang@intel.com>; devel@edk2.groups.io
>Subject: Re: [edk2-devel] [PATCH] MdePkg-UefiSpec.h: Add UEFI 2.8 new
>memory attributes
>
>Qing:
>  Thanks for your update. Reviewed-by: Liming Gao <liming.gao@intel.com>
>
>Thanks
>Liming
>>-----Original Message-----
>>From: Huang, Qing
>>Sent: Wednesday, October 30, 2019 12:55 PM
>>To: devel@edk2.groups.io
>>Cc: Gao, Liming <liming.gao@intel.com>
>>Subject: [PATCH] MdePkg-UefiSpec.h: Add UEFI 2.8 new memory attributes
>>
>>BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=2309
>>Add EFI_MEMORY_SP and EFI_MEMORY_CPU_CRYPTO definition into UEFI
>>specification header file.
>>
>>Signed-off-by: Qing Huang <qing.huang@intel.com>
>>Cc: Liming Gao <liming.gao@intel.com>
>>---
>> MdePkg/Include/Uefi/UefiSpec.h | 20 ++++++++++++++++++++
>> 1 file changed, 20 insertions(+)
>>
>>diff --git a/MdePkg/Include/Uefi/UefiSpec.h
>>b/MdePkg/Include/Uefi/UefiSpec.h
>>index 44a0a6a7fa..5d58faf7ed 100644
>>--- a/MdePkg/Include/Uefi/UefiSpec.h
>>+++ b/MdePkg/Include/Uefi/UefiSpec.h
>>@@ -82,6 +82,26 @@ typedef enum {
>> // If all memory has the same reliability, then this bit is not used.
>> //
>> #define EFI_MEMORY_MORE_RELIABLE    0x0000000000010000ULL
>>+
>>+//
>>+// Note: UEFI spec 2.8 and following:
>>+//
>>+// Specific-purpose memory (SPM). The memory is earmarked for
>>+// specific purposes such as for specific device drivers or applications.
>>+// The SPM attribute serves as a hint to the OS to avoid allocating this
>>+// memory for core OS data or code that can not be relocated.
>>+//
>>+#define EFI_MEMORY_SP               0x0000000000040000ULL
>>+//
>>+// If this flag is set, the memory region is capable of being
>>+// protected with the CPU’s memory cryptographic
>>+// capabilities. If this flag is clear, the memory region is not
>>+// capable of being protected with the CPU’s memory
>>+// cryptographic capabilities or the CPU does not support CPU
>>+// memory cryptographic capabilities.
>>+//
>>+#define EFI_MEMORY_CPU_CRYPTO       0x0000000000080000ULL
>>+
>> //
>> // Runtime memory attribute
>> //
>>--
>>2.17.0.windows.1
>
>
>


      parent reply	other threads:[~2019-11-04  2:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30  4:54 [PATCH] MdePkg-UefiSpec.h: Add UEFI 2.8 new memory attributes Huang, Qing
2019-10-30  5:45 ` Liming Gao
     [not found] ` <15D256836EC4F298.17962@groups.io>
2019-11-04  2:08   ` Liming Gao [this message]

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=4A89E2EF3DFEDB4C8BFDE51014F606A14E536943@SHSMSX104.ccr.corp.intel.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