Add the EFI_RESOURCE_ATTRIBUTE_SPECIAL_PURPOSE attribute.

[Patrick-Payne]

Description

Add the EFI_RESOURCE_ATTRIBUTE_SPECIAL_PURPOSE resource attribute as per the PI 1.8 spec. This flag is used to indicate that the memory should be treated as special purpose memory (SPM).

Also adds GCD code that marks the SPM with the EFI_MEMORY_SP bit in the memory map and sets the GCD memory type to EfiGcdMemoryTypeSystemMemory.

• Impacts functionality?
  • Functionality - Does the change ultimately impact how firmware functions?
  • This change impacts how special purpose memory is represented in HOBs and in the memory map.
• Impacts security?
  • Security - Does the change have a direct security impact on an application,
    flow, or firmware?
  • Examples: Crypto algorithm change, buffer overflow fix, parameter
    validation improvement, ...
• Breaking change?
  • Breaking change - Will anyone consuming this change experience a break
    in build or boot behavior?
  • Examples: Add a new library class, move a module to a different repo, call
    a function in a new library class in a pre-existing module, ...
• Includes tests?
  • Tests - Does the change include any explicit test code?
  • Examples: Unit tests, integration tests, robot tests, ...
• Includes documentation?
  • Documentation - Does the change contain explicit documentation additions
    outside direct code modifications (and comments)?
  • Examples: Update readme file, add feature readme file, link to documentation
    on an a separate Web page, ...

How This Was Tested

stuart_ci_build passed clean.

Manual testing using UEFI firmware on a device showed the expected behavior when HOBs are marked with EFI_RESOURCE_ATTRIBUTE_SPECIAL_PURPOSE.

Integration Instructions

N/A

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 15 lines in your changes are missing coverage. Please review.

Project coverage is 1.22%. Comparing base (4ef1dc9) to head (73fd883).

Files	Patch %	Lines
MdeModulePkg/Core/Dxe/Gcd/Gcd.c	0.00%	15 Missing ⚠️

Additional details and impacted files

@@                Coverage Diff                 @@
##           release/202311     #851      +/-   ##
==================================================
- Coverage            1.22%    1.22%   -0.01%     
==================================================
  Files                1303     1303              
  Lines              335695   335701       +6     
  Branches             3189     3189              
==================================================
  Hits                 4118     4118              
- Misses             331501   331507       +6     
  Partials               76       76              

Flag	Coverage Δ
MdeModulePkg	0.68% <0.00%> (-0.01%)	⬇️
MdePkg	5.37% <ø> (ø)
NetworkPkg	0.00% <ø> (ø)
PolicyServicePkg	30.41% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[os-d]

Can you add [CHERRY-PICK] to the commit title that was cherry-picked from edk2? Additionally, can you wrap each of the changes in your commit with:

// MU_CHANGE BEGIN: Add EFI_MEMORY_SP
...
// MU_CHANGE END: Add EFI_MEMORY_SP

Or for single line changes:

...; // MU_CHANGE: Add EFI_MEMORY_SP

This helps us track what to upstream to edk2 and how to integrate it when we pull down new edk2 releases.