u-boot.git/include/efi_selftest.h, branch v2018.09

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

efi_loader: supply EFI network test

2017-10-09T05:00:36+00:00

This patch provides an EFI application to check the correct function
of the Simple Network Protocol implementation.

It sends a DHCP request and analyzes the DHCP offer.

Different error conditions including a 10s timeout are checked.

A successful execution will look like this:

=> bootefi nettest
Scanning disk ide.blk#0...
Found 1 disks
WARNING: Invalid device tree, expect boot to fail
Network test
DHCP Discover
DHCP reply received from 192.168.76.2 (52:55:c0:a8:4c:02)
as broadcast message.
OK. The test was completed successfully.

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

efi_selftest: correct definition of efi_st_error

2017-10-09T05:00:35+00:00

Enclose definition in parantheses to allow using efi_st_error
like a void function.

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

efi_selftest: make tests easier to read

2017-10-09T05:00:23+00:00

Rename counter to more illustrative names.
Update notification function description.
Simplify notification function.
Add comment for arbitrary non-zero value.
Document @return.
Use constants for return values of setup, execute, teardown.

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

efi_selftest: provide an EFI selftest application

2017-09-18T21:53:57+00:00

A testing framework for the EFI API is provided.
It can be executed with the 'bootefi selftest' command.

It is coded in a way that at a later stage we may turn it
into a standalone EFI application. The current build system
does not allow this yet.

All tests use a driver model and are run in three phases:
setup, execute, teardown.

A test may be setup and executed at boottime,
it may be setup at boottime and executed at runtime,
or it may be setup and executed at runtime.

After executing all tests the system is reset.

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