On 06/24/13 23:06, Jordan Justen wrote: > On Mon, Jun 24, 2013 at 6:12 AM, Laszlo Ersek <[email protected]> wrote: >> ... I think I can see interaction between ReserveEmuVariableNvStore(), >> FvbInitialize(), and LoadNvVarsFromFs() now. When >> ReserveEmuVariableNvStore() runs after VM reboot, AllocateRuntimePool() >> will return the same address (overlaying the previous memory buffer) >> because it runs "early on". What an exorbitant hack! > > Indeed. Unfortunately, it was the only sort of "non-volatile" variable > support that we had initially. > > We could consider yanking all these hacks out, and just forcing people > to use QEMU with flash support when that eventually gets finished. > > But, some people like the idea that the 'disk image' can decide the > boot order, so I'm not sure what the eventual solution will be.
I think we should keep (improving) the on-disk NvVars stuff until the flash support is complete. BTW could you please summarize the status on that? I believe KVM and qemu already have the necessary commits (could you identify them perhaps?) and that you have a WIP series for OVMF -- what needs to be done there? CC'ing Gleb and Paolo. Thanks! Laszlo ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
