#4672: Thread-local storage should be usable once an idle thread exists
-----------------------------+------------------------------
Reporter: Sebastian Huber | Owner: Sebastian Huber
Type: defect | Status: closed
Priority: normal | Milestone: 6.1
Component: score | Version: 6
Severity: normal | Resolution: fixed
Keywords: | Blocked By:
Blocking: 4560, 4668 |
-----------------------------+------------------------------
Changes (by Sebastian Huber <sebastian.huber@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"03e4d1e931cdd6582ccc92b3a4dc883b446b5647/rtems"
03e4d1e9/rtems]:
{{{
#!CommitTicketReference repository="rtems"
revision="03e4d1e931cdd6582ccc92b3a4dc883b446b5647"
score: Add _CPU_Use_thread_local_storage()
At some point during system initialization, the idle threads are created.
Afterwards, the boot processor basically executes within the context of an
idle
thread with thread dispatching disabled. On some architectures, the
thread-local storage area of the associated thread must be set in
dedicated
processor registers. Add the new CPU port function to do this:
void _CPU_Use_thread_local_storage( const Context_Control *context )
Close #4672.
}}}
--
Ticket URL: <http://devel.rtems.org/ticket/4672#comment:3>
RTEMS Project <http://www.rtems.org/>
RTEMS Project
_______________________________________________
bugs mailing list
[email protected]
http://lists.rtems.org/mailman/listinfo/bugs
