| Karl Zhang | 3de5ab1 | 2021-05-31 11:45:48 +0800 | [diff] [blame^] | 1 | ####################### |
| 2 | 'calls'-directory guide |
| 3 | ####################### |
| 4 | |
| 5 | ************ |
| 6 | Introduction |
| 7 | ************ |
| 8 | |
| 9 | These classes define objects that describe everything needed to generate a PSA |
| 10 | call. The Parse phase, which parses the test-template file, generates an C++ |
| 11 | STL ``vector`` of ``psa_call``-class objects describing the series of PSA calls |
| 12 | chosen for the test to run, based upon the test template and the random seed. |
| 13 | |
| 14 | More-specifically class psa_class is an abstract class, and this vector contains |
| 15 | objects of derived classes, each derived class defining a particular call type. |
| 16 | Each ``psa_call``-subclass object encapsulates the initial and expected data, |
| 17 | expected pass/fail results, and other information about the call. |
| 18 | |
| 19 | ********************************************** |
| 20 | ``.../tools/tf_fuzz/calls`` directory contents |
| 21 | ********************************************** |
| 22 | .. code-block:: bash |
| 23 | |
| 24 | crypto_call.cpp psa_call.cpp security_call.cpp sst_call.cpp |
| 25 | crypto_call.hpp psa_call.hpp security_call.hpp sst_call.hpp |
| 26 | |
| 27 | In the future, it's probably possible to, for target systems that can support |
| 28 | sufficiently large memory footprints, instead of writing these calls out to a |
| 29 | ``.c`` file, to directly execute these PSA calls. |
| 30 | |
| 31 | -------------- |
| 32 | |
| 33 | *Copyright (c) 2020, Arm Limited. All rights reserved.* |