TF-A and TF-A Tests git repositories are getting moved to a TF-A/
namespace in order to easily identify what repos are for TF-A or TF-M.

Change-Id: Id3e9ae299fa4e0dd8699c967879cd8ce5a17c940
Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>

John Tsichritzis authored Oct 25, 2018 and Sandrine Bailleux committed Nov 06, 2018

Change-Id: Id05eebb811d4c23c6a2bfdfb4762bb659b97a4bf
Signed-off-by: John Tsichritzis <john.tsichritzis@arm.com>

Jeenu Viswambharan authored Oct 16, 2018 and Sandrine Bailleux committed Oct 31, 2018

EL3 runtime firmware currently enables unconditional access to pointer
authentication registers from lower EL [1]. The test performs a read
access on a pointer authentication system register to ensure that the
access is permitted from a lower EL, and doesn't result in a trap to
EL3.

[1] https://github.com/ARM-software/arm-trusted-firmware/commit/3ff4aaaca44b75504aec5ab5b72cd587a6fcd432



Change-Id: I893604ebcd9e5df830d97cce405c2a7518c0b23c
Signed-off-by: Jeenu Viswambharan <jeenu.viswambharan@arm.com>

Change-Id: I54b213bbdb13e21d8d0919b76eebf6c85e1fa691
Signed-off-by: Sathees Balya <sathees.balya@arm.com>

Print the cluster and cpu ID in the output.  It is useful to know
which cpu is part of which cluster as that helps with the data
visualization.

Change-Id: Id02745d677abc4d4e9c2e289917da6d67e7b93b2
Signed-off-by: Dimitris Papastamos <dimitris.papastamos@arm.com>

At the moment, alignment fault checking is always enabled in TF-A
Tests (by setting the HSCTLR/SCTLR.A bit). Thus, for every instruction
that loads or stores one or more registers, the hardware checks that
the address being accessed is properly aligned to the size of the data
element(s) being accessed. If this check fails it causes an alignment
fault, which is taken as a data abort exception.

However, the compiler is currently unaware that it must not emit load
and store instructions resulting in unaligned accesses because we do
not compile the source code with -mstrict-align (AArch64) /
-mno-unaligned-access (AArch32). Because of this, we might get some
unexpected alignment faults.

We could request the compiler to align all data accesses but whether
this gives us any performance benefit is dependent on the
microarchitecture. Thus, it is simpler to just disable hardware
alignment checking and let the compiler make the call.

Change-Id: I6ef4afb09e0f87c8462a968da1ca2192ee075b40
Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>

Mention this as a known issue in the change log.

Also update the run_fwu_fvp.sh script to invoke the revB version
of the FVP rather than the revC.

Change-Id: I58957f4ac3ee37e054fe33bfb246c6f6fc689fdd
Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>

Sathees Balya authored Oct 16, 2018 and Sandrine Bailleux committed Oct 19, 2018

Remove the default value of CROSS_COMPILE from EL3 Makefile
and use the user-defined value.

Change-Id: Icaed8aec0a82293dbefc579b89d0eef23c676f6a
Signed-off-by: Sathees Balya <sathees.balya@arm.com>

Change-Id: Ifb9658f09c6de61f8ca4b36966f9a8d9987992d5
Signed-off-by: John Tsichritzis <john.tsichritzis@arm.com>

Change-Id: I40631d9c1d99e24311d158cec5a47b433d6fe328
Signed-off-by: John Tsichritzis <john.tsichritzis@arm.com>

Change-Id: If9f6dfa4547e4ed62764cf8dc2fd0b767134b2e7
Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>

Sample output:

> make help_tests
Available sets of tests:
 - sdei
 - uncontainable
 - extensive
 - arm-state-switch
 - manual
 - single-fault
 - tsp
 - psci-extensive
 - standard
 - cpu-extensions
 - boot-req
 - psci
 - tftf-validation
 - spm
 - el3-power-state
 - performance
 - template
 - fwu
 - runtime-instrumentation

Change-Id: I8ab5ae0cadfe950cb690d0943148b15e2448f5c8
Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>

"common" might mean "shared", when we really want to say
"ordinary", "frequent".

Change-Id: If3cdb1693eb24ecb55b6145386bcf6a6a17c6d74
Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>

The build system now supports building a TFTF binary with a subset of
tests. The chosen subset may be specified through the TESTS variable,
e.g.:

 make TESTS=sdei tftf
 make TESTS=tsp tftf
 make TESTS=cpu-extensions tftf

This will use tftf/tests/tests-${TESTS}.xml as the tests manifest
          and tftf/tests/tests-${TESTS}.mk as the tests makefile.

This provides more flexibility than before. It is still possible to
compile all the tests using:

 make TESTS=common tftf

It's also possible to include the extensive tests using:

 make TESTS=extensive tftf

If TESTS is not specified, it defaults to the 'common' tests.

Change-Id: Ifcdc52e9a29ed5f9a9bf57703cdb109b5a169fa2
Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>

Introduce makefiles for 2 popular sets of tests: the standard tests
and the extensive ones.

Change-Id: I529a1583a1b20838c60f06654d3f47f4041fb9bc
Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>

Instead of unconditionally pulling all test source files in tests.mk,
introduce small makefiles that pull in only those source files that
are required to test a particular feature. For every tests manifest
(test-*.xml files), create the associated makefile.

The main benefit is to compile only the required test source files
when selecting a subset of the tests. For example, if one selects the
SDEI XML file, the TFTF binary only needs the SDEI test cases.

Change-Id: I281eb50846edea2d238c86a795fde8747f8b420b
Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>

This test was pinned to Juno and was not included for other
platforms. In reality, it only relies on a GICv2 to be present but
does nothing specific to Juno beyond that.

Instead, we now dynamically detect the GIC version inside the test
function and skip it if it is not GICv2. The test is now part of the
generic TSP testsuite.

With the test being available to all platforms, the Juno tests XML
file is now empty, as it only contained this one test. Therefore, we
remove it.

Change-Id: I8b8f0eac905cfff8a87a2305cb2abf4bb9353ef1
Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>

In practice, all the functions in this file are platform-specific. It is
better to force all platforms to implement than having some sort of weak
function placeholder.

Porting guide updated.

Change-Id: I5beeeb10bec6fe5178b24503d6da8ca66074a8c6
Signed-off-by: Antonio Nino Diaz <antonio.ninodiaz@arm.com>

As we are using common functions for performing the various
test-cases, we cannot use __func__ directly in those functions.  To
differentiate the test-cases in the final output, we need the name of
test to be passed all the way down to the output function.

Change-Id: Ia0c3dabeddf2e25b4aa395103c5261575ad6cac6
Signed-off-by: Dimitris Papastamos <dimitris.papastamos@arm.com>

This is the first public version of the tests for the Trusted
Firmware-A project. Please see the documentation provided in the
source tree for more details.

Change-Id: I6f3452046a1351ac94a71b3525c30a4ca8db7867
Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>
Co-authored-by: amobal01 <amol.balasokamble@arm.com>
Co-authored-by: Antonio Nino Diaz <antonio.ninodiaz@arm.com>
Co-authored-by: Asha R <asha.r@arm.com>
Co-authored-by: Chandni Cherukuri <chandni.cherukuri@arm.com>
Co-authored-by: David Cunado <david.cunado@arm.com>
Co-authored-by: Dimitris Papastamos <dimitris.papastamos@arm.com>
Co-authored-by: Douglas Raillard <douglas.raillard@arm.com>
Co-authored-by: dp-arm <dimitris.papastamos@arm.com>
Co-authored-by: Jeenu Viswambharan <jeenu.viswambharan@arm.com>
Co-authored-by: Jonathan Wright <jonathan.wright@arm.com>
Co-authored-by: Kévin Petit <kevin.petit@arm.com>
Co-authored-by: Roberto Vargas <roberto.vargas@arm.com>
Co-authored-by: Sathees Balya <sathees.balya@arm.com>
Co-authored-by: Shawon Roy <Shawon.Roy@arm.com>
Co-authored-by: Soby Mathew <soby.mathew@arm.com>
Co-authored-by: Thomas Abraham <thomas.abraham@arm.com>
Co-authored-by: Vikram Kanigiri <vikram.kanigiri@arm.com>
Co-authored-by: Yatharth Kochar <yatharth.kochar@arm.com>