patina-v2.0.0

What's Changed

• chore: Release 1.0.1 @os-d (#474)
  
  Change Details

    ## Description

  @cfernald forgot :)

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?

  How This Was Tested

  N/A.

  Integration Instructions

  See release notes.
  

  
  

  ---

  
  

⚠️ Breaking Changes

• Move MM code to `components/patina_mm` [Rebase \& FF] @makubacki (#475)
  
  Change Details

    ## Description

  Closes #443

  Moves the MM component code from patina_sdk to a new patina_mm crate.

  Marked as a breaking change due to modifications in public namespace.

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?

  How This Was Tested

  • cargo make all
  • Tests pass.
  • Review patina_mm documentation.

  Integration Instructions

  Use the new paths in patina_mm when access MM components, config, and services.
  

  
  

  ---

  
  

🔐 Security Impacting

• [REBASE \& FF] Image Loader: Remove Runtime Image Memory Protections on EBS @os-d (#447)
  
  Change Details

    ## Description

  This PR consists of three commits:

  Dispatcher: Reduce Depex Evaluation Message to Trace

  One of the noisest logs in the patina boot currently is the log that says a depex guid was evaluated, which in general does not provide useful information to an average build. This commit moves that to a trace log.

  GCD: Update Compatibility Mode to Allow For Unaligned Loader Allocations

  In the case of loader code and data allocations having been made before compatibility mode is activated, the current GCD code does not ensure that these returned ranges are page_aligned (they may be missing the allocator node length), so this updates the logic to apply compatibility mode to page aligned lengths and addresses.

  Image Loader: Remove Runtime Image Memory Protections on EBS

  edk2 follows a pattern where runtime image memory protections are removed on ExitBootServices to allow the SetVirtualAddressMap callback to relocate runtime images. Patina was not following this, which only matters for certain flavors of Linux, it could cause the core to attempt to write to RO memory.

  For now, Patina follows the same method as edk2, but investigation is happening to determine if we should have a different method.

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?

  How This Was Tested

  Tested booting TinyLinux on SBSA.

  Integration Instructions

  N/A.
  

  
  

  ---

  
  

Full Changelog: patina-v1.0.1...v2.0.0