[Task]: Remaining Perf Work

Feature Overview

1. Ability to publish the FBPT as a fallback if perf tracing is "disabled".
2. Install the FPDT when perf tracing is "enabled".
3. Add FPDT report status code listeners. Make sure all status code are picked up.

• Note: We do not support S3 in Patina. As a result, we do not support lock box (lock box is more generic than S3 but that was the main use case, and we've rejected it).

• Note: Try to avoid the EFI_FIRMWARE_PERFORMANCE_VARIABLE_NAME variable implementation in Rust code. We should not share pointers between modules using UEFI variables.

• Goal: We eliminate all C performance - DxeCorePerformanceLib (already done), DxePerformanceLib (already done), FirmwarePerformanceDataTableDxe.

Today:

• DxeCorePerformanceLib - Used by the DXE core only to acquire perf records from MM with the communicate service and from PEI using the HOB list. Installs the performance protocol. Installs the gPerformanceProtocolGuid EFI configuration table.
• DxePerformanceLib - Used by non-core DXE drivers to report performance records. Wraps the performance protocol so they don't have to deal with it.
• FirmwarePerformanceDataTableDxe - Installs the FBPT (in case it is not already installed), FPDT, and S3PT.

Urgency

Medium

Are you going to implement the feature request?

Someone else needs to implement the feature

Do you need maintainer feedback?

No maintainer feedback needed

Anything else?

No response

Start by locating the Rust implementations corresponding to DxeCorePerformanceLib, DxePerformanceLib, and FirmwarePerformanceDataTableDxe, then trace the existing FBPT, FPDT, and S3PT installation paths. Compare the current behavior with the three requested capabilities and verify that every FPDT status code is handled; done means the C performance components are eliminated without relying on S3, lock box, or EFI performance-variable pointer sharing.