EFI memory map compatibility

[retrage]

@retrage After your last commit I have to admit I didn't retest Windows. Did it work for you? I get the following error:

<INSTANCE CLASSNAME="BLUESCREEN">                                               
<PROPERTY NAME="STOPCODE" TYPE="string"><VALUE>"0x1E"</VALUE></PROPERTY><machine-info>
<name>WIN-L3C8M6IQS0Q</name>                                                    
<guid>00000000-0000-0000-0000-000000000000</guid>                               
<processor-architecture>AMD64</processor-architecture>
<os-version>10.0</os-version>
<os-build-number>17763</os-build-number>
<os-product>Windows Server 2019</os-product>
<os-service-pack>None</os-service-pack>
</machine-info>

</INSTANCE>
</BP>
!SAC>
KMODE_EXCEPTION_NOT_HANDLED


0xFFFFFFFFC0000005
0xFFFFF8024AEB51F1
0x0000000000000000
0x000000000011A0D0

Going back to 282ebc0 makes Windows boot fine. So I think there needs to be a little bit more refinement on the memory map.

Originally posted by @rbradford in #114 (comment)

[retrage]

Both Linux and Windows also use MemoryAttributeTable along with an EFI memory map to set the RuntimeServices page attributes.