public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: Andrew Fish <afish@apple.com>, edk2-devel <edk2-devel@lists.01.org>
Subject: Re: OEM EFI_STATUS Code Ranges?
Date: Fri, 23 Feb 2018 08:22:43 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E1CEDAF@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <827D6636-D89F-442B-B9FA-5542007C4B8A@apple.com>

Andrew:
  PI, DXE and BASE status code macro are added to define their status code. 

  Now, there is no OEM status code definition. So, OEM status code macro is not added. Have you the usage on OEM status macro?

Thanks
Liming
>-----Original Message-----
>From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
>Andrew Fish
>Sent: Tuesday, February 20, 2018 8:20 AM
>To: edk2-devel <edk2-devel@lists.01.org>
>Subject: [edk2] OEM EFI_STATUS Code Ranges?
>
>I noticed the edk2 is missing UEFI defined ranges for OEM EFI_STATUS Code
>Ranges.
>
>~/work/src/edk2/MdePkg(master)>git grep MAX_BIT -- *.h
>Include/AArch64/ProcessorBind.h:84:#define MAX_BIT
>0x8000000000000000ULL
>Include/Arm/ProcessorBind.h:139:#define MAX_BIT      0x80000000
>Include/Base.h:977:#define ENCODE_ERROR(StatusCode)
>((RETURN_STATUS)(MAX_BIT | (StatusCode)))
>Include/Ebc/ProcessorBind.h:94:#define MAX_BIT     ((UINTN)((1ULL <<
>(sizeof (INTN) * 8 - 1))))
>Include/Ia32/ProcessorBind.h:238:#define MAX_BIT     0x80000000
>Include/Ipf/ProcessorBind.h:228:#define MAX_BIT     0x8000000000000000ULL
>Include/Pi/PiMultiPhase.h:42:#define DXE_ERROR(StatusCode)  (MAX_BIT |
>(MAX_BIT >> 2) | StatusCode)
>Include/Pi/PiMultiPhase.h:60:#define PI_ENCODE_WARNING(a)
>((MAX_BIT >> 2) | (a))
>Include/Pi/PiMultiPhase.h:67:#define PI_ENCODE_ERROR(a)
>(MAX_BIT | (MAX_BIT >> 2) | (a))
>Include/X64/ProcessorBind.h:252:#define MAX_BIT
>0x8000000000000000ULL
>
>
>Is there a reason the OEM ranges never got added?
>
>#define OEM_ENCODE_ERROR(a)                  (MAX_BIT | (MAX_BIT >> 1) | (a))
>#define OEM_ENCODE_WARNING(a)              ((MAX_BIT >> 1) | (a))
>
>
>
>
>Thanks,
>
>Andrew Fish
>_______________________________________________
>edk2-devel mailing list
>edk2-devel@lists.01.org
>https://lists.01.org/mailman/listinfo/edk2-devel


      reply	other threads:[~2018-02-23  8:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20  0:19 OEM EFI_STATUS Code Ranges? Andrew Fish
2018-02-23  8:22 ` Gao, Liming [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=4A89E2EF3DFEDB4C8BFDE51014F606A14E1CEDAF@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