efi_loader: describe returning of control
Provide a sober description of how control can be returned by a UEFI binary. Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
This commit is contained in:
parent
d417b94e57
commit
55111c5052
|
|
@ -2933,10 +2933,10 @@ efi_status_t EFIAPI efi_start_image(efi_handle_t image_handle,
|
||||||
ret = EFI_CALL(image_obj->entry(image_handle, &systab));
|
ret = EFI_CALL(image_obj->entry(image_handle, &systab));
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* Usually UEFI applications call Exit() instead of returning.
|
* Control is returned from a started UEFI image either by calling
|
||||||
* But because the world doesn't consist of ponies and unicorns,
|
* Exit() (where exit data can be provided) or by simply returning from
|
||||||
* we're happy to emulate that behavior on behalf of a payload
|
* the entry point. In the latter case call Exit() on behalf of the
|
||||||
* that forgot.
|
* image.
|
||||||
*/
|
*/
|
||||||
return EFI_CALL(systab.boottime->exit(image_handle, ret, 0, NULL));
|
return EFI_CALL(systab.boottime->exit(image_handle, ret, 0, NULL));
|
||||||
}
|
}
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue