diff options
| author | Heinrich Schuchardt | 2020-01-10 22:06:54 +0100 |
|---|---|---|
| committer | Heinrich Schuchardt | 2020-01-15 00:51:51 +0100 |
| commit | 55111c5052b3a6b6d26daacc1950e30a2c3aa55f (patch) | |
| tree | 9f8fb6db3921eb177b2e4ab7c39498cc7aacf7a1 | |
| parent | d417b94e57748486021859af7fe9c512cee9f4f2 (diff) | |
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>
| -rw-r--r-- | lib/efi_loader/efi_boottime.c | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/lib/efi_loader/efi_boottime.c b/lib/efi_loader/efi_boottime.c index 3103a50158a..1f598b357a5 100644 --- a/lib/efi_loader/efi_boottime.c +++ b/lib/efi_loader/efi_boottime.c @@ -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)); /* - * Usually UEFI applications call Exit() instead of returning. - * But because the world doesn't consist of ponies and unicorns, - * we're happy to emulate that behavior on behalf of a payload - * that forgot. + * Control is returned from a started UEFI image either by calling + * Exit() (where exit data can be provided) or by simply returning from + * the entry point. In the latter case call Exit() on behalf of the + * image. */ return EFI_CALL(systab.boottime->exit(image_handle, ret, 0, NULL)); } |