Add reference to test hooks in detailed design

Signed-off-by: David Horstmann <david.horstmann@arm.com>
This commit is contained in:
David Horstmann 2023-10-23 20:08:38 +01:00
parent 806055edbf
commit 8f905c289d

View File

@ -501,7 +501,9 @@ This should either poison or unpoison the given buffer based on the value of `sh
* When `should_poison == 1`, this is equivalent to calling `VALGRIND_MAKE_MEM_NOACCESS(buffer, length)` or `ASAN_POISON_MEMORY_REGION(buffer, length)`. * When `should_poison == 1`, this is equivalent to calling `VALGRIND_MAKE_MEM_NOACCESS(buffer, length)` or `ASAN_POISON_MEMORY_REGION(buffer, length)`.
* When `should_poison == 0`, this is equivalent to calling `VALGRIND_MAKE_MEM_DEFINED(buffer, length)` or `ASAN_UNPOISON_MEMORY_REGION(buffer, length)`. * When `should_poison == 0`, this is equivalent to calling `VALGRIND_MAKE_MEM_DEFINED(buffer, length)` or `ASAN_UNPOISON_MEMORY_REGION(buffer, length)`.
We may choose one of two approaches: The PSA copying function must then have test hooks implemented as outlined in [Validation of copying by memory poisoning](#validation-of-copying-by-memory-poisoning).
For test implementation, we may choose one of two approaches:
* Use transparent allocation-based memory poisoning. * Use transparent allocation-based memory poisoning.
* Use memory poisoning functions and a new testsuite. * Use memory poisoning functions and a new testsuite.