From 8f905c289d7ba60d339a7906836b3922f81a05a0 Mon Sep 17 00:00:00 2001 From: David Horstmann Date: Mon, 23 Oct 2023 20:08:38 +0100 Subject: [PATCH] Add reference to test hooks in detailed design Signed-off-by: David Horstmann --- docs/architecture/psa-shared-memory.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/architecture/psa-shared-memory.md b/docs/architecture/psa-shared-memory.md index 9929573fc0..dd2f87f2a8 100644 --- a/docs/architecture/psa-shared-memory.md +++ b/docs/architecture/psa-shared-memory.md @@ -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 == 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 memory poisoning functions and a new testsuite.