zephyr/tests/kernel
Daniel Leung 65f6e3a4e3 tests: mem_map: compare just written data too in mapped_rw
After writing to mapped_rw, we should also check if the backing
buffer has the correct data. Or we could have a situation where
on systems that need explicit cache controls, the newly updated
mapped_rw is cached but the backing buffer still contain old
data. Comparing the backing buffer to mapped_ro does not really
matter in this case as the content would certain match.

Also, this moves the mapping of mapped_ro earlier so that we
map both mapped_rw and mapped_ro because data manipulation.

And that we also need to verify the values of the backing and
mapped buffers.

Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2022-11-05 19:56:57 +01:00
..
common tests: arc: enable previously disabled tests on ARCv3 64bit platforms 2022-10-31 11:22:12 +01:00
condvar/condvar_api tests: move to using CONFIG_MP_MAX_NUM_CPUS 2022-10-20 22:04:10 +09:00
context tests: move to using CONFIG_MP_MAX_NUM_CPUS 2022-10-20 22:04:10 +09:00
device ztest: improve some tests 2022-09-09 07:05:38 -04:00
early_sleep tests: kernel: cleanup test meta-data 2022-11-04 22:13:54 -04:00
events tests: kernel: cleanup test meta-data 2022-11-04 22:13:54 -04:00
fatal tests: kernel: fatal: cleanup test configuration 2022-11-04 22:13:54 -04:00
fifo tests: kernel: cleanup test meta-data 2022-11-04 22:13:54 -04:00
fpu_sharing tests: move to using CONFIG_MP_MAX_NUM_CPUS 2022-10-20 22:04:10 +09:00
gen_isr_table tests: kernel: cleanup test meta-data 2022-11-04 22:13:54 -04:00
interrupt tests: kernel: cleanup test meta-data 2022-11-04 22:13:54 -04:00
lifo tests: kernel: cleanup test meta-data 2022-11-04 22:13:54 -04:00
mbox tests: kernel: cleanup test meta-data 2022-11-04 22:13:54 -04:00
mem_heap tests: kernel: cleanup test meta-data 2022-11-04 22:13:54 -04:00
mem_protect tests: mem_map: compare just written data too in mapped_rw 2022-11-05 19:56:57 +01:00
mem_slab tests: kernel: cleanup test meta-data 2022-11-04 22:13:54 -04:00
mp tests: kernel: cleanup test meta-data 2022-11-04 22:13:54 -04:00
msgq tests: kernel: cleanup test meta-data 2022-11-04 22:13:54 -04:00
mutex tests: kernel: mutex: move race timeout test to mutex_api 2022-10-31 21:23:29 -04:00
obj_tracking tests: Add CONFIG_PIPES to tests that use pipes 2022-08-17 19:31:25 +02:00
pending tests: move to using CONFIG_MP_MAX_NUM_CPUS 2022-10-20 22:04:10 +09:00
pipe tests: move to using CONFIG_MP_MAX_NUM_CPUS 2022-10-20 22:04:10 +09:00
poll tests: move to using CONFIG_MP_MAX_NUM_CPUS 2022-10-20 22:04:10 +09:00
profiling/profiling_api
queue ztest: remove the obsolete NULL appended to zassert macros 2022-09-09 07:05:38 -04:00
sched tests: kernel: schedule_api: fix filter 2022-11-05 13:44:14 -04:00
semaphore tests/semaphore: fix "cpu test took too long" assertion failure 2022-09-28 07:53:56 +00:00
sleep tests: move to using CONFIG_MP_MAX_NUM_CPUS 2022-10-20 22:04:10 +09:00
smp tests: kernel: cleanup test meta-data 2022-11-04 22:13:54 -04:00
smp_boot_delay tests: kernel: smp_boot_delay: Convert CONFIG_MP_NUM_CPUS handling 2022-10-31 17:09:06 +01:00
spinlock tests: kernel: spinlock: Convert CONFIG_MP_NUM_CPUS handling 2022-10-31 17:09:06 +01:00
stack/stack tests: move to using CONFIG_MP_MAX_NUM_CPUS 2022-10-20 22:04:10 +09:00
threads smp: Move for loops to use arch_num_cpus instead of CONFIG_MP_NUM_CPUS 2022-10-21 13:14:58 +02:00
tickless/tickless_concept tests: move to using CONFIG_MP_MAX_NUM_CPUS 2022-10-20 22:04:10 +09:00
timer tests: kernel: cleanup test meta-data 2022-11-04 22:13:54 -04:00
usage/thread_runtime_stats tests: move to using CONFIG_MP_MAX_NUM_CPUS 2022-10-20 22:04:10 +09:00
workq tests: kernel: cleanup test meta-data 2022-11-04 22:13:54 -04:00
xip tests: kernel: cleanup test meta-data 2022-11-04 22:13:54 -04:00