DxePagingAuditTestApp: Remove MemoryOutsideEfiMemoryMapIsInaccessible Test

[os-d]

Description

MemoryOutsideEfiMemoryMapIsInaccessible was attempting to test that memory outside the EFI_MEMORY_MAP was marked EFI_MEMORY_RP or unmapped, however this is not a valid test as we expect there to be ranges outside of the EFI_MEMORY_MAP, such as GCD non-existent memory and non-runtime MMIO ranges. This patch removes the test. Closes #531.

• Impacts functionality?
  • Functionality - Does the change ultimately impact how firmware functions?
  • Examples: Add a new library, publish a new PPI, update an algorithm, ...
• 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

Tested on Q35.

Integration Instructions

N/A.

[kuqin12]

I thought this is a valid test just that our core does not support it yet? Although, it probably does not matter if we change the page table mapping logic (not to map all pages).

[os-d]

I thought this is a valid test just that our core does not support it yet? Although, it probably does not matter if we change the page table mapping logic (not to map all pages).

No, this isn’t valid. We expect some memory outside of the EFI_MEMORY_MAP to have valid mappings, like non-runtime MMIO.

[TaylorBeebe]

I thought this is a valid test just that our core does not support it yet? Although, it probably does not matter if we change the page table mapping logic (not to map all pages).

No, this isn’t valid. We expect some memory outside of the EFI_MEMORY_MAP to have valid mappings, like non-runtime MMIO.

If this requirement is being relaxed, you may also want to remove requirements 4 and 9 from the Enhanced Memory Protection documentation: https://microsoft.github.io/mu/WhatAndWhy/enhancedmemoryprotection/