OvmfPkg: rename QemuBootOrderNNNN to VMMBootOrderNNNN
While the actual implementation (using qemu fw_cfg) is qemu-specific, the idea to store the boot order as configured by the VMM in EFI variables is not. So lets give the variables a more neutral name while we still can (i.e. no stable tag yet with the new feature). While being at it also fix the NNNN format (use %x instead of %d for consistency with BootNNNN). Signed-off-by: Gerd Hoffmann <kraxel@redhat.com> Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
This commit is contained in:
committed by
mergify[bot]
parent
3361336607
commit
406ad0582a
@ -1709,7 +1709,7 @@ FreeFwCfg:
|
||||
Attempt to retrieve the "bootorder" fw_cfg file from QEMU. Translate
|
||||
the OpenFirmware device paths therein to UEFI device path fragments.
|
||||
|
||||
On Success store the device path in QemuBootOrderNNNN variables.
|
||||
On Success store the device path in VMMBootOrderNNNN variables.
|
||||
**/
|
||||
VOID
|
||||
EFIAPI
|
||||
@ -1794,13 +1794,13 @@ StoreQemuBootOrder (
|
||||
UnicodeSPrint (
|
||||
VariableName,
|
||||
sizeof (VariableName),
|
||||
L"QemuBootOrder%04d",
|
||||
L"VMMBootOrder%04x",
|
||||
VariableIndex++
|
||||
);
|
||||
DEBUG ((DEBUG_INFO, "%a: %s = %s\n", __FUNCTION__, VariableName, Translated));
|
||||
gRT->SetVariable (
|
||||
VariableName,
|
||||
&gQemuBootOrderGuid,
|
||||
&gVMMBootOrderGuid,
|
||||
EFI_VARIABLE_BOOTSERVICE_ACCESS | EFI_VARIABLE_RUNTIME_ACCESS,
|
||||
GetDevicePathSize (DevicePath),
|
||||
DevicePath
|
||||
|
Reference in New Issue
Block a user