spec:/acfg/val/acfg

Tests the effect of application configuration options. More...

Files
file	tc-acfg.c

Functions
	T_TEST_CASE (AcfgValAcfg)

Detailed Description

Tests the effect of application configuration options.

This test case performs the following actions:

• Check the effect of application configuration options. In addition, this test case validates the effect of CONFIGURE_INIT. The test case includes rtems/confdefs.h without defining CONFIGURE_INIT before the include. If this header would define configuration data structures, then linking the test suite executable would result in multiple definition errors. This header is included in the test suite runner translation unit while CONFIGURE_INIT is defined before the include. If this would not result in the definition of application defined configuration data structures, then the checks below for non-default settings would fail.
  • Check the default value CONFIGURE_IDLE_TASK_BODY where the optional BSP-provided default value is enabled.
  • Check the configured CONFIGURE_INIT_TASK_ARGUMENTS. This validates also the effect of CONFIGURE_INIT_TASK_ENTRY_POINT and CONFIGURE_RTEMS_INIT_TASKS_TABLE.
  • Check the configured CONFIGURE_INIT_TASK_INITIAL_MODES.
  • Check the configured CONFIGURE_INIT_TASK_NAME.
  • Check the configured CONFIGURE_INIT_TASK_PRIORITY. A priority of zero can only be set for system tasks. This validates also CONFIGURE_INIT_TASK_ATTRIBUTES.
  • Check that the configured CONFIGURE_MINIMUM_TASKS_WITH_USER_PROVIDED_STORAGE value reduced the stack space size.
  • Check the configured CONFIGURE_MAXIMUM_BARRIERS value.
  • Check the configured CONFIGURE_MAXIMUM_USER_EXTENSIONS value.
  • Check the configured CONFIGURE_MAXIMUM_MESSAGE_QUEUES value.
  • Check the configured CONFIGURE_MAXIMUM_PARTITIONS value.
  • Check the configured CONFIGURE_MAXIMUM_PERIODS value.
  • Check the default CONFIGURE_MAXIMUM_PORTS value.
  • Check the configured CONFIGURE_MAXIMUM_PROCESSORS value.
  • Check the default CONFIGURE_MAXIMUM_REGIONS value.
  • Check the configured CONFIGURE_MAXIMUM_SEMAPHORES value.
  • Check the configured CONFIGURE_MAXIMUM_TASKS value.
  • Check the configured CONFIGURE_MAXIMUM_TIMERS value.
  • Check the configured CONFIGURE_MICROSECONDS_PER_TICK value in microseconds.
  • Check the configured CONFIGURE_MICROSECONDS_PER_TICK value in milliseconds.
  • Check the configured CONFIGURE_MICROSECONDS_PER_TICK value in nanoseconds.
  • Check the configured CONFIGURE_TASK_STACK_ALLOCATOR hook. Using the test stack allocator validates also spec:/acfg/if/init-task-construct-storage-size, since the test_task_stack_allocate() allocate handler only supports CONFIGURE_MAXIMUM_TASKS minus one stacks and the validation test for spec:/rtems/task/req/create-errors creates for some pre-condition variants all tasks until RTEMS_TOO_MANY is returned. In addition, test_task_stack_allocate() checks that the allocation size is greater than or equal to TEST_MINIMUM_STACK_SIZE which validates CONFIGURE_MINIMUM_TASK_STACK_SIZE.
  • Check the configured CONFIGURE_TASK_STACK_ALLOCATOR_AVOIDS_WORK_SPACE value.
  • Check the configured CONFIGURE_TASK_STACK_DEALLOCATOR hook.
  • Check the configured CONFIGURE_TASK_STACK_ALLOCATOR_FOR_IDLE hook.
  • Check the configured CONFIGURE_IDLE_TASK_STACK_SIZE value.
  • Check the configured CONFIGURE_INTERRUPT_STACK_SIZE value.
  • Check the configured CONFIGURE_TICKS_PER_TIMESLICE value.