public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Andrew Fish <afish@apple.com>
To: "Gao, Liming" <liming.gao@intel.com>
Cc: edk2-devel <edk2-devel@lists.01.org>
Subject: Re: Missing PI definitions?
Date: Tue, 04 Dec 2018 17:04:19 -0800	[thread overview]
Message-ID: <3D1412E2-64CE-4912-B823-73BDCCC3706A@apple.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E383BF2@SHSMSX104.ccr.corp.intel.com>

Liming,

Sorry I guess I was confusing this with EFI_RESOURCE_ATTRIBUTE_TESTED. 

I'll a little confused that it is implementation given it is passed into gDS->AddMemorySpace() the PI Spec defines the values of Capabilities to be defined in the UEFI Spec. as the GetMemoryMap() attributes. It is not clear that the implementation actually owns these bits? Almost feels like we should update the PI spec to include these #defines. 

I seem to remember we have been using these bits for a long time.....

Thanks,

Andrew Fish

> On Dec 4, 2018, at 4:19 PM, Gao, Liming <liming.gao@intel.com> wrote:
> 
> Andrew:
>  UEFI spec doesn't define them. They are the implement related definitions. They are not required to be exposed to OS. We can add one header file in MdeModulePkg to share them between DxeCore and MemoryTest driver. Besides, ECP package will be retired. There is no change for it. 
> 
> #define EFI_MEMORY_PRESENT      0x0100000000000000ULL
> #define EFI_MEMORY_INITIALIZED  0x0200000000000000ULL
> #define EFI_MEMORY_TESTED       0x0400000000000000ULL
> 
> Thanks
> Liming
>> -----Original Message-----
>> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org <mailto:edk2-devel-bounces@lists.01.org>] On Behalf Of
>> Andrew Fish



      reply	other threads:[~2018-12-05  1:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 16:00 Missing PI definitions? Andrew Fish
2018-12-05  0:19 ` Gao, Liming
2018-12-05  1:04   ` Andrew Fish [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=3D1412E2-64CE-4912-B823-73BDCCC3706A@apple.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