Redfish error report lib

[nicklela]

Server usually has its own error logging mechanism. Although Redfish has error report definition. Do we consider to create a library so plat form can link to their own error logging system?

[nicklela]

We can use REPORT_STATUS_CODE_XXX() defined in edk2/MdePkg/Include/Library/ReportStatusCodeLib.h to return Redfish errors. When BMC follows ARM SBMR specification, these progress code can be logged in BMC.

[nicklela]

Possible solution:

• F.2 Boot progress code format - Arm® Server Base Manageability Requirements 2.0
• PLDM event log mechanism

[nicklela]

@changab, @wangsim is working on this and we are using boot progress code. Not sure if you check PLDM evet path or not...

[nicklela]

This is how edk2 does this:

https://github.com/nicklela/edk2-redfish-client/blob/99bc4c50e80ff25d8dfc1cd5b02cceb6d2eb3482/MdePkg/Include/Pi/PiStatusCode.h#L100-L108

https://github.com/nicklela/edk2-redfish-client/blob/99bc4c50e80ff25d8dfc1cd5b02cceb6d2eb3482/MdeModulePkg/MdeModulePkg.dec#L1470-L1480

[nicklela]

After discussion, we can send RFC to edk2-devel and propose to add Manageability status code to PiStatusCode.h

[nicklela]

PI status code proposal for manageability is here: https://github.com/nicklela/edk2/pull/4/files

The usage is:

Feature driver -> REPORT_STATUS_CODE_WITH_EXTENDED_DATA() -> edk2 status code driver -> platform status code worker.

[nicklela]

RFC is posted and positive feedbacks are received. The suggestion is to follow EDK II Code First Process and submit change request to PI specification: https://edk2.groups.io/g/rfc/message/804