On 05/07/2022 00:33, Chris Johns wrote:
On 4/7/2022 4:08 pm, Sebastian Huber wrote:
On 29/06/2022 15:07, Sebastian Huber wrote:
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.
Any comments to this patch?
I did wonder about the boot processor executing within the idle thread's context
comment.
What code is the boot processor executing in the context of the idle thread?
The device driver initialization and creation of "/dev/console" is done
in this context for example.
How does that execution effect the stack allocated to the idle thread?
The idle stack is not used. The system initialization uses the interrupt
stacks.
I have always considered the idle thread's stack as small because it does
nothing.
Chris
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.hu...@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
