[Bug 3987] Adds a new memory allocation boot service GetMemoryMapEx that carries a memory feature support bitmap.



--- Comment #21 from ardb@... ---
(In reply to Dionna Glaze from comment #20)
So is self-report kernel binary bit still an option?
It's unlikely, but maybe we can convince Linux upstream that it's really
necessary. There's a mechanism for it in the boot protocol called

Shall we also consider the minimal amount of the memory that kernel needs. So that FW can accept that amount of memory then let OS handle the left unaccept-mem.
We could add a 64-bit entry in kernel_info called required_accepted_memory
and only have it be non-zero if the kernel supports unaccepted memory.

Ard, what do you think about this? I think since it involves necessary
information for booting (accepting the right amount of memory), this should
fit in the boot protocol.
I'm skeptical but perhaps you could elaborate on the execution flow in this
case? Who checks this bit and when/where? And how about other OSes or
architectures? (note that "we don't care" is a valid response but it has to be

You are receiving this mail because:
You are on the CC list for the bug.