Hi,
> Ovmf can interpret the existence of an opt/ovmf/unaccepted_memory file
> I think "false" can mean either accept all memory or "do what you need
> to" and negotiate if the memory map boot service can create unaccepted
> memory entries. Whichever appears supported.
> Then "true" can be "do whatever, including creating unaccepted memory
> entries in the memory map".
>
> That seems the simplest way to allow a configuration of this feature.
Well, we actually have three states: file is not present, file is
present and true, file is present and false. The existing options
use CamelCase, so we should stick to that. A name which makes clear
what the option does would be good I think. So, how about this:
opt/ovmf/AcceptAllMemory=true
ovmf must accept all memory.
opt/ovmf/AcceptAllMemory=false
ovmf should pass memory above 4G as unaccepted
memory to the guest os.
opt/ovmf/AcceptAllMemory not present
ovmf can choose what to do (including negotiate).
take care,
Gerd
