xtest/perfs: fix option for random initialization of input buffers
Before this change, AES and SHA performance tests always filled
input buffers with random values, wherever option "-r" was set or
not.
This change allows the run SHA performance test with zero-initialized
input buffers or random-initialized input buffers.
This change allows the run AES performance test with zero-initialized
input buffers, random-initialized input buffers or with uninitialized
input buffers (which is quite handy when testing with input buffers
into SDP secure memory).
A new option is added in "xtest --aes-perf": argument "--not-inited"
specifies that input buffer does not need to be initialized.
Since the initialization of crypto test buffers can use several
configuration, this change clarifies then, renaming the macro
CRYPTO_NOT_RANDOM into CRYPTO_USE_ZEROS.
Signed-off-by: Etienne Carriere <etienne.carriere@linaro.org>
Reviewed-by: Jerome Forissier <jerome.forissier@linaro.org>
diff --git a/host/xtest/crypto_common.h b/host/xtest/crypto_common.h
index 096c27b..c686c84 100644
--- a/host/xtest/crypto_common.h
+++ b/host/xtest/crypto_common.h
@@ -38,8 +38,9 @@
#define CRYPTO_DEF_LOOPS 1 /* Default amount of inner loops */
+#define CRYPTO_USE_ZEROS 0 /* Init input data to zero */
#define CRYPTO_USE_RANDOM 1 /* Get input data from /dev/urandom */
-#define CRYPTO_NOT_RANDOM 0
+#define CRYPTO_NOT_INITED 2 /* Input data are not initialized */
#define CRYPTO_DEF_WARMUP 2 /* Start with a 2-second busy loop */
#define CRYPTO_DEF_COUNT 5000 /* Default number of measurements */