CYGPKG_KERNEL_THREADS
Dummy
There are a number of configuration options related to the implementation of threads, for example whether or not the eCos kernel supports per-thread data.
CYGFUN_KERNEL_THREADS_TIMER
Boolean
This option controls whether or not the kernel should support per-thread clock and alarm related functions. Also some of the synchronization primitives such as semaphore and condition variable timed wait operations require per-thread timer support. If none of these facilities are required then the option can be disabled.
CYGVAR_KERNEL_THREADS_NAME
Boolean
Threads may optionally be supplied with a name string that is used to identify them during debugging. This name is only present if `this option is defined. Disabling it reduces both code and data size.
CYGVAR_KERNEL_THREADS_LIST
Boolean
Threads may optionally be placed on a housekeeping list so that all threads may be located easily. This is useful mainly in conjunction with source-level debugging.
CYGFUN_KERNEL_THREADS_STACK_LIMIT
Boolean
This option makes the kernel keep track of the lower limit on each thread"s stack. It allows the kernel to adjust the lower limit, thus making space for per-thread data. Note that it does not imply any form of run-time stack overflow checking.
CYGVAR_KERNEL_THREADS_DATA
Boolean
It is possible for the kernel to support per-thread data, in other words an area of memory specific to each thread which can be used to store data for that thread. This per-thread data can be used by applications or by other packages such as the ISO C library.
CYGNUM_KERNEL_THREADS_DATA_MAX
Count
It is possible for the kernel to support per-thread data, in other words an area of memory specific to each thread which can be used to store data for that thread. This per-thread data can be used by applications or by other packages such as the ISO C library. This configuration option controls the number of words of per-thread data that the kernel will allow.
CYGNUM_KERNEL_THREADS_IDLE_STACK_SIZE
Count
This configuration option specifies the stack size in bytes for the idle thread. Unless the HAL is configured to use a separate interrupt stack this size must be sufficient to meet the requirements of all interrupt handlers - these requirements are cumulative if nested interrupted are enabled. Depending on the target architecture, the stack size typically has to be a multiple of eight or sixteen bytes. This will be overridden where it is used if the architectural HAL requires a minimum stack size to handle interrupts correctly.