diff options
| author | jljusten <jljusten@6f19259b-4bc3-4df7-8a09-765794883524> | 2009-09-26 07:15:55 +0000 |
|---|---|---|
| committer | jljusten <jljusten@6f19259b-4bc3-4df7-8a09-765794883524> | 2009-09-26 07:15:55 +0000 |
| commit | 9607962def9f847c243b9fecb590c0cf94eec4fc (patch) | |
| tree | 14e8488f9882ce5a59dc0bfbd89a90237b26c431 /OvmfPkg/EmuVariableFvbRuntimeDxe | |
| parent | 27f58ea1b22a59f6eb1950a6af2a47e3dc9b70c1 (diff) | |
| download | edk2-9607962def9f847c243b9fecb590c0cf94eec4fc.tar.gz edk2-9607962def9f847c243b9fecb590c0cf94eec4fc.tar.bz2 edk2-9607962def9f847c243b9fecb590c0cf94eec4fc.zip | |
OVMF: Add support for saving the NV variables to disk following each SetVariable call.
Note:
* This only works before ExitBootServices
* For OVMF, variables are only preserved on the disk if there
is a hard disk connected which has a writeable FAT file system.
The Ovmf/Library/EmuVariableFvbLib library will look for the
gUefiOvmfPkgTokenSpaceGuid.PcdEmuVariableEvent PCD to be set to
a non-zero value. If set, it is treated as an event handle, and
each write to the EmuVariableFvb will cause the event to be
signaled.
In this change, the OVMF platform BDS library sets up this event,
and sets the PCD so that after each write to the EMU Variable FVB,
the non-volatile variables will be saved out to the file system.
The end result is that NV variables that are written prior to the
ExitBootServices call should be preserved by storing them on the
disk.
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@9318 6f19259b-4bc3-4df7-8a09-765794883524
Diffstat (limited to 'OvmfPkg/EmuVariableFvbRuntimeDxe')
0 files changed, 0 insertions, 0 deletions