public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kun Qin" <kuqin12@gmail.com>
To: devel@edk2.groups.io
Cc: Andrew Fish <afish@apple.com>, Leif Lindholm <leif@nuviainc.com>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Liming Gao <gaoliming@byosoft.com.cn>,
	Zhiguang Liu <zhiguang.liu@intel.com>
Subject: [PATCH v3 0/2] EDK2 Code First: PI Specification: Expand PI Status Codes
Date: Thu,  3 Feb 2022 11:03:01 -0800	[thread overview]
Message-ID: <20220203190303.2008-1-kuqin12@gmail.com> (raw)

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3794

This patch series is a rebase of previous submission:
https://edk2.groups.io/g/devel/message/85335

In current Status Codes definitions of PI spec v1.7 errata, there are a
few instances where the software could trigger system reboots while the
corresponding case were not covered by the already defined status codes.

One scenario that OEMs would be interested is that fragmented memory map
from boot to boot would fail to meet certain OS ACPI requirements (i.e.
S4 resume boot requires consistent memory maps) and trigger system
reboots. Yet the corresponding case was not covered by the already
defined status codes.

The unexpected system reboots above could indicate decay of system health
and reporting of such generic events would provide helpful information to
OEMs to investigate/prevent system failures in general.

The change intends to expand definitions of `EFI_SW_EC_**` under Status
Codes to cover more unexpected system reboot events, which could improve
Status Code futility and readability.

Compared to previous series, v3 patch changes mainly include:
a. Added BZ3794 prefix for newly added macro definitions;

Patch v3 branch: https://github.com/kuqin12/edk2/tree/BZ3794-expand_status_codes_v3

Cc: Andrew Fish <afish@apple.com>
Cc: Leif Lindholm <leif@nuviainc.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Cc: Zhiguang Liu <zhiguang.liu@intel.com>

Kun Qin (2):
  EDK2 Code First: PI Specification: New error codes of Host Software
    class
  MdePkg: MmCommunication: Add new Host Software class Error Code to
    MdePkg

 CodeFirst/BZ3794-SpecChange.md   | 55 ++++++++++++++++++++
 MdePkg/Include/Pi/PiStatusCode.h |  1 +
 2 files changed, 56 insertions(+)
 create mode 100644 CodeFirst/BZ3794-SpecChange.md

-- 
2.34.1.windows.1


             reply	other threads:[~2022-02-03 19:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 19:03 Kun Qin [this message]
2022-02-03 19:03 ` [PATCH v3 1/2] EDK2 Code First: PI Specification: New error codes of Host Software class Kun Qin
2022-02-03 19:03 ` [PATCH v3 2/2] MdePkg: MmCommunication: Add new Host Software class Error Code to MdePkg Kun Qin

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=20220203190303.2008-1-kuqin12@gmail.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