[Bug 1924] Enhanced stack allocator configuration
bugzilla-daemon at rtems.org
bugzilla-daemon at rtems.org
Wed Nov 9 14:38:59 UTC 2011
https://www.rtems.org/bugzilla/show_bug.cgi?id=1924
Gedare <gedare at rtems.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gedare at rtems.org
--- Comment #3 from Gedare <gedare at rtems.org> 2011-11-09 08:38:58 CST ---
(In reply to comment #2)
> Created attachment 1370 [details]
> Configuration changes.
>
> This patch adds the following fields to the Configuration:
>
> + /** This field specifies the size in bytes of the RTEMS thread stack space.
> + */
> + uintptr_t stack_space_size;
> +
> + /**
> + * @brief Specifies if a unified work area is used or not.
> + *
> + * If this element is @a true, then the RTEMS Workspace and the C Program
> + * Heap use the same heap, otherwise they use separate heaps.
> + */
> + bool unified_work_area;
> +
> + /**
> + * @brief Specifies if the stack allocator avoids the work space.
> + *
> + * If this element is @a true, then the stack allocator must not allocate
> the
> + * thread stacks from the RTEMS Workspace, otherwise it should allocate the
> + * thread stacks from the RTEMS Workspace.
> + */
> + bool stack_allocator_avoids_work_space;
>
> The unified_work_area field replaces the rtems_unified_work_area global
> variable.
>
> The work space estimate is split up into a separate work and stack space
> estimate.
>
> A new CONFIGURE_TASK_STACK_ALLOCATOR_AVOIDS_WORK_SPACE configuration define is
> available.
This makes sense to me. It is hard to follow the diff through confdefs though,
so I guess we'll see what the final result looks like...
Inline routines might be better than macros for getting and setting
configuration variables, but that is a minor nit.
--
Configure bugmail: https://www.rtems.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
More information about the bugs
mailing list