So this is just junk unallocated memory that we are reporting as
a type it *could* be if an allocation occurs to minimize failures
of ExitBootServices. Which is questionable. But in terms of
attributes, I would expect we either have this unallocated
memory marked the same as the bin type or better, mark it RP
if we can (Taylor is making a change to set RP on free memory
by default, so we would have this in the page table, but we
would need to decide what we tell the OS).

[Ray] When reviewing today's logic of memory protection through page table, I feel that it was designed improperly in the beginning.

My rough thought is:

* All memory is RP initially (as you said Taylor will do that)

* Allocated memory is mapped as either RO or XD, depending on code/data. Or RP if it's a guard page.

Maybe I am not aware of some limitations of the above idea. The limitations prevented the initial design be in this way.

Or what Taylor will do aligns to the idea?

Thanks,
Ray