zephyr

History

Anas Nashif 66cfcc26bc tests: introduce Makefile.test To customise test builds and support test related features such as time stamps and a boot banner, introduce a Makefile variant that is dedicated to testing. Initially we introduce a new config overlay that is used for all tests, in this case we enable BOOT_BANNER and BUILD_TIMESTAMP. This will print the current version and the date, useful when reporting bugs and also an indicator that the system has booted before the test has started. For example: [QEMU] CPU: qemu32 *** BOOTING ZEPHYR OS v1.6.99 - BUILD: Dec 21 2016 19:57:13 *** tc_start() - Test Nanokernel CPU and thread routines Initializing nanokernel objects ... .. Change-Id: I224318cdeb55a301964ea366dbc577e2e3a09175 Signed-off-by: Anas Nashif <anas.nashif@intel.com>		2017-01-03 17:48:44 +00:00
..
src	tests: kernel: test_slab: Porting memory map tests to unified	2016-12-24 15:16:02 +00:00
Makefile	tests: introduce Makefile.test	2017-01-03 17:48:44 +00:00
README.txt	tests: kernel: test_slab: Porting memory map tests to unified	2016-12-24 15:16:02 +00:00
prj.conf	tests: kernel: test_slab: Porting memory map tests to unified	2016-12-24 15:16:02 +00:00
testcase.ini	tests: kernel: test_slab: Porting memory map tests to unified	2016-12-24 15:16:02 +00:00

README.txt

Title: Memory Slab APIs

Description:

This test verifies that the kernel memory slab APIs operate as expected.

--------------------------------------------------------------------------------

Building and Running Project:

This microkernel project outputs to the console.  It can be built and executed
on QEMU as follows:

    make qemu

--------------------------------------------------------------------------------

Troubleshooting:

Problems caused by out-dated project information can be addressed by
issuing one of the following commands then rebuilding the project:

    make clean          # discard results of previous builds
                        # but keep existing configuration info
or
    make pristine       # discard results of previous builds
                        # and restore pre-defined configuration info

--------------------------------------------------------------------------------

Sample Output:

tc_start() - Test Kernel memory slabs
Starts RegressionTask
===================================================================
(1) - Allocate and free 2 blocks in <RegressionTask>
===================================================================
Function testSlabGetAllBlocks
MAP_LgBlks used 0 blocks
  k_mem_slab_alloc OK, p[0] = 0x00104e00
MAP_LgBlks used 1 blocks
  k_mem_slab_alloc OK, p[1] = 0x00104a00
MAP_LgBlks used 2 blocks
  k_mem_slab_alloc RC_FAIL expected as all (2) blocks are used.
===================================================================
printPointers: p[0] = 0x00104e00, p[1] = 0x00104a00,
===================================================================
Function testSlabFreeAllBlocks
MAP_LgBlks used 2 blocks
  block ptr to free p[0] = 0x00104e00
MAP_LgBlks freed 1 block
MAP_LgBlks used 1 blocks
  block ptr to free p[1] = 0x00104a00
MAP_LgBlks freed 2 block
MAP_LgBlks used 0 blocks
===================================================================
Starts HelperTask
===================================================================
(2) - Allocate 2 blocks in <HelperTask>
===================================================================
Function testSlabGetAllBlocks
MAP_LgBlks used 0 blocks
  k_mem_slab_alloc OK, p[0] = 0x00104a00
MAP_LgBlks used 1 blocks
  k_mem_slab_alloc OK, p[1] = 0x00104e00
MAP_LgBlks used 2 blocks
  k_mem_slab_alloc RC_FAIL expected as all (2) blocks are used.
===================================================================
===================================================================
(3) - Further allocation results in  timeout in <RegressionTask>
===================================================================
RegressionTask: k_mem_slab_alloc times out which is expected
RegressionTask: start to wait for block
===================================================================
(4) - Free a block in <HelperTask> to unblock the other task from alloc timeout
===================================================================
HelperTask: About to free a memory block
RegressionTask: k_mem_slab_alloc OK, block allocated at 0x00104a00
RegressionTask: start to wait for block
===================================================================
(5) <HelperTask> freeing the next block
===================================================================
HelperTask: About to free another memory block
RegressionTask: k_mem_slab_alloc OK, block allocated at 0x00104e00
HelperTask: freed all blocks allocated by this task
===================================================================
PASS - HelperTask.
RegressionTask: Used 2 block
RegressionTask: 1 block freed, used 1 block
===================================================================
PASS - RegressionTask.
===================================================================
PROJECT EXECUTION SUCCESSFUL