public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kun Qin" <kuqin12@gmail.com>
To: devel@edk2.groups.io, michael.d.kinney@intel.com
Cc: Andrew Fish <afish@apple.com>, Leif Lindholm <leif@nuviainc.com>,
	"Gao, Liming" <gaoliming@byosoft.com.cn>,
	"Liu, Zhiguang" <zhiguang.liu@intel.com>
Subject: Re: [edk2-devel] [PATCH v2 1/2] EDK2 Code First: PI Specification: New error codes of Host Software class
Date: Tue, 25 Jan 2022 10:42:10 -0800	[thread overview]
Message-ID: <83861bc8-ddfe-5f9b-2d4d-159b194b8128@gmail.com> (raw)
In-Reply-To: <CO1PR11MB49299B111008540E2D7ACA46D2589@CO1PR11MB4929.namprd11.prod.outlook.com>

Hi Mike,

Sorry if the questions are being naive. My interpretation for the 
code-first process below is that we need to first obtain "Reviewed-By" 
tags for all patches in this branch on this mailing list, is that correct?

If so, do you mind provide rb tags or other feedback for them? Or if 
there is a designated panel to review code-first changes, could you 
please let me know where the name list is? Otherwise, please advise.

Thanks in advance.

Regards,
Kun

On 01/18/2022 14:43, Michael D Kinney wrote:
> The spec and code changes need to be put together in the edk2-staging repository
> following the process here:
> 
> 	https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Code-First-Process
> 
> Once we have Reviewed-by from community for the spec and code changes and everything
> is checked into the edk2-staging repository, platforms can test the changes and provide
> feedback.  The amount of testing required depends on the complexity of the change.
> Once testing requirements have been met, it is ready for UEFI Forum review of the
> content in edk2-staging.
> 
> 
> Mike
> 
>> -----Original Message-----
>> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Kun Qin
>> Sent: Tuesday, January 18, 2022 11:00 AM
>> To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>
>> Cc: Andrew Fish <afish@apple.com>; Leif Lindholm <leif@nuviainc.com>; Gao, Liming <gaoliming@byosoft.com.cn>; Liu, Zhiguang
>> <zhiguang.liu@intel.com>
>> Subject: Re: [edk2-devel] [PATCH v2 1/2] EDK2 Code First: PI Specification: New error codes of Host Software class
>>
>> Hi Mike,
>>
>> Do you have further feedback regarding this updated change? If not,
>> could you please shed some light on how to proceed on this code first PI
>> spec change request?
>>
>> Any help is appreciated.
>>
>> Regards,
>> Kun
>>
>> On 01/07/2022 17:32, Kun Qin via groups.io wrote:
>>> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3794
>>>
>>> This change includes specification update markdown file that describes
>>> the proposed PI Specification v1.7 Errata A in detail and potential
>>> impact to the existing codebase.
>>>
>>> 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>
>>>
>>> Signed-off-by: Kun Qin <kuqin12@gmail.com>
>>> ---
>>>
>>> Notes:
>>>       v2:
>>>       - Removed "RELEASE_ASSERT" definition
>>>       - Removed reference to EDK2 based memory type info [Mike]
>>>
>>>    CodeFirst/BZ3794-SpecChange.md | 55 ++++++++++++++++++++
>>>    1 file changed, 55 insertions(+)
>>>
>>> diff --git a/CodeFirst/BZ3794-SpecChange.md b/CodeFirst/BZ3794-SpecChange.md
>>> new file mode 100644
>>> index 000000000000..61a0be798d7f
>>> --- /dev/null
>>> +++ b/CodeFirst/BZ3794-SpecChange.md
>>> @@ -0,0 +1,55 @@
>>> +# Title: Introduction of `EFI_SW_EC_FRAGMENTED_MEMORY_MAP` Status Code
>>> +
>>> +## Status: Draft
>>> +
>>> +## Document: UEFI Platform Initialization Specification Version 1.7 Errata A
>>> +
>>> +## License
>>> +
>>> +SPDX-License-Identifier: CC-BY-4.0
>>> +
>>> +## Submitter: [TianoCore Community](https://www.tianocore.org)
>>> +
>>> +## Summary of the change
>>> +
>>> +Add `EFI_SW_EC_FRAGMENTED_MEMORY_MAP` into Status Codes definition.
>>> +
>>> +## Benefits of the change
>>> +
>>> +Current Status Codes covered various [software class error code
>> definitions](https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Pi/PiStatusCode.h).
>>> +
>>> +However, 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 request of this 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.
>>> +
>>> +## Impact of the change
>>> +
>>> +Occupy a new macro definitions of Error Codes under Software class Status Codes.
>>> +
>>> +## Detailed description of the change [normative updates]
>>> +
>>> +### Specification Changes
>>> +
>>> +1. In PI Specification v1.7 Errata A: Vol. 3, Table 3-61: Error Code Operations: Host Software Class, add one new rows below
>> `EFI_SW_EC_FV_CORRUPTED` definition:
>>> +
>>> +    | Operation | Description | Extended Data |
>>> +    | --- | --- | --- |
>>> +    | EFI_SW_EC_FRAGMENTED_MEMORY_MAP | System will reboot due to fragmented memory maps | None |
>>> +
>>> +1. In PI Specification v1.7 Errata A: Vol. 3, Table 3-61: Error Code Operations: Host Software Class, replace the row of
>> `0x0014-0x00FF` to:
>>> +
>>> +    | Operation | Description | Extended Data |
>>> +    | --- | --- | --- |
>>> +    | 0x0015-0x00FF | Reserved for future use by this specification for Host Software class error codes. | None |
>>> +
>>> +1. In PI Specification v1.7 Errata A: Vol. 3, Section 6.7.4.3 Error Code Definitions: Prototype, add one new definitions below
>> `EFI_SW_EC_FV_CORRUPTED` definition:
>>> +
>>> +    ```c
>>> +    #define EFI_SW_EC_FRAGMENTED_MEMORY_MAP  0x00000014
>>> +    ```
>>> +
>>> +### Code Changes
>>> +
>>> +1. Add macro definitions in `MdePkg/Include/Pi/PiStatusCode.h` to match new specification.
>>
>>
>>
>>
> 
> 
> 
> 
> 
> 

      reply	other threads:[~2022-01-25 18:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-08  1:32 [PATCH v2 0/2] EDK2 Code First: PI Specification: Update EFI_MM_COMMUNICATE_HEADER Kun Qin
2022-01-08  1:32 ` [PATCH v2 1/2] EDK2 Code First: PI Specification: New error codes of Host Software class Kun Qin
2022-01-08  1:32 ` [PATCH v2 2/2] MdePkg: MmCommunication: Add new Host Software class Error Code to MdePkg Kun Qin
     [not found] ` <16C82792D4F086F3.710@groups.io>
2022-01-18 19:00   ` [edk2-devel] [PATCH v2 1/2] EDK2 Code First: PI Specification: New error codes of Host Software class Kun Qin
2022-01-18 22:43     ` Michael D Kinney
2022-01-25 18:42       ` Kun Qin [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=83861bc8-ddfe-5f9b-2d4d-159b194b8128@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