u-boot.git/include/efi_selftest.h, branch v2020.01

efi_selftest: remove redundant function efi_st_memcmp()

2019-05-07T19:10:04+00:00

Function memcmp() is available in efi_freestanding.c. So we do not remove a
further implementation.

Replace all usages of efi_st_memcmp() by memcmp().

Signed-off-by: Heinrich Schuchardt

efi_selftest: test exit_data

2019-05-02T16:17:50+00:00

Amend the unit test 'start image exit' to transfer a string as exit data.

Signed-off-by: Heinrich Schuchardt

efi_selftest: do not write to linker generated array

2018-12-02T20:59:37+00:00

Linker generated arrays may be stored in code sections of memory that are
not writable. So let's allocate setup_ok as an array at runtime.

This avoids an illegal memory access observed in the sandbox.

Reported-by: Simon Glass 
Signed-off-by: Heinrich Schuchardt 
Signed-off-by: Alexander Graf

efi_selftest: refactor text input test

2018-09-23T19:55:30+00:00

Move reusable utility functions to efi_selftest_util.c.

Signed-off-by: Heinrich Schuchardt 
Signed-off-by: Alexander Graf

efi_loader: struct efi_simple_text_input_protocol

2018-09-23T19:55:29+00:00

%s/efi_simple_input_interface/efi_simple_text_input_protocol/

We should be consistent in the naming of the EFI protocol interface
structures. The protocol is called EFI_SIMPLE_TEXT_INPUT_PROTOCOL.

%s/ExtendedVerification/extended_verification/

Use consistent naming of function parameters. Do not use CamelCase.

Signed-off-by: Heinrich Schuchardt 
Signed-off-by: Alexander Graf

SPDX: Convert a few files that were missed before

2018-05-11T00:38:35+00:00

As part of the main conversion a few files were missed.  These files had
additional whitespace after the '*' and before the SPDX tag and my
previous regex was too strict.  This time I did a grep for all SPDX tags
and then filtered out anything that matched the correct styles.

Fixes: 83d290c56fab ("SPDX: Convert all of our single license tags to Linux Kernel style")
Reported-by: Heinrich Schuchardt 
Signed-off-by: Tom Rini

efi_selftest: do not execute test if setup failed

2018-04-23T19:34:28+00:00

Executing a test after failed setup may lead to unexpected behavior like
an illegal memory access. So after a setup failure we should skip to
teardown.

Signed-off-by: Heinrich Schuchardt 
Signed-off-by: Alexander Graf

efi_selftest: colored test output

2018-01-22T22:09:12+00:00

Add color coding to output:
test section    blue
success         green
errors          red
todo            yellow
summary         white
others          light gray

Signed-off-by: Heinrich Schuchardt 
Reviewed-by: Simon Glass 
[agraf: Fold in move of set_attribute before the print]
Signed-off-by: Alexander Graf

efi_selftest: test protocol management

2017-12-01T12:22:55+00:00

This unit test checks the following protocol services:
InstallProtocolInterface, UninstallProtocolInterface,
InstallMultipleProtocolsInterfaces,
UninstallMultipleProtocolsInterfaces,
HandleProtocol, ProtocolsPerHandle,
LocateHandle, LocateHandleBuffer.

As UninstallProtocolInterface and UninstallMultipleProtocolsInterfaces
are not completely implemented a TODO message will shown for
their failure.

Signed-off-by: Heinrich Schuchardt 
Signed-off-by: Alexander Graf

efi_selftest: allow to select a single test for execution

2017-12-01T12:22:55+00:00

Environment variable efi_selftest is passed as load options
to the selftest application. It is used to select a single
test to be executed.

The load options are an UTF8 string. Yet I decided to keep
the name propertiy of the tests as char[] to reduce code
size.

Special value 'list' displays a list of all available tests.

Tests get an on_request property. If this property is set
the tests are only executed if explicitly requested.

The invocation of efi_selftest is changed to reflect that
bootefi selftest with efi_selftest = 'list' will call the
Exit bootservice.

Signed-off-by: Heinrich Schuchardt 
Signed-off-by: Alexander Graf