Searched hist:d86a240aec6e0e26027c9f2b5444eb2e8a4b1301 (Results 1 – 4 of 4) sorted by relevance
| /haiku/src/system/kernel/arch/riscv64/ |
| H A D | arch_thread.cpp | d86a240aec6e0e26027c9f2b5444eb2e8a4b1301 Wed Mar 29 15:24:17 UTC 2023 Augustin Cavalier <waddlesplash@gmail.com> kernel/thread: Refactor thread-local-storage initialization and updating.
* TLS slots are not in any way architecture-specific; we do not even
have a mechanism by which they could be made so at present.
Thus, the initialization of them can be moved to common code, and
out of the per-architecture implementations.
* When dealing with a fork()ed thread, it will already have a TLS array
with values set in it. Therefore, do not overwrite the whole array,
but instead only update the specific values which have changed on fork.
This fixes at least part of #17896.
|
| /haiku/src/system/kernel/arch/arm/ |
| H A D | arch_thread.cpp | d86a240aec6e0e26027c9f2b5444eb2e8a4b1301 Wed Mar 29 15:24:17 UTC 2023 Augustin Cavalier <waddlesplash@gmail.com> kernel/thread: Refactor thread-local-storage initialization and updating.
* TLS slots are not in any way architecture-specific; we do not even
have a mechanism by which they could be made so at present.
Thus, the initialization of them can be moved to common code, and
out of the per-architecture implementations.
* When dealing with a fork()ed thread, it will already have a TLS array
with values set in it. Therefore, do not overwrite the whole array,
but instead only update the specific values which have changed on fork.
This fixes at least part of #17896.
|
| /haiku/src/system/kernel/arch/x86/ |
| H A D | arch_thread.cpp | d86a240aec6e0e26027c9f2b5444eb2e8a4b1301 Wed Mar 29 15:24:17 UTC 2023 Augustin Cavalier <waddlesplash@gmail.com> kernel/thread: Refactor thread-local-storage initialization and updating.
* TLS slots are not in any way architecture-specific; we do not even
have a mechanism by which they could be made so at present.
Thus, the initialization of them can be moved to common code, and
out of the per-architecture implementations.
* When dealing with a fork()ed thread, it will already have a TLS array
with values set in it. Therefore, do not overwrite the whole array,
but instead only update the specific values which have changed on fork.
This fixes at least part of #17896.
|
| /haiku/src/system/kernel/ |
| H A D | thread.cpp | d86a240aec6e0e26027c9f2b5444eb2e8a4b1301 Wed Mar 29 15:24:17 UTC 2023 Augustin Cavalier <waddlesplash@gmail.com> kernel/thread: Refactor thread-local-storage initialization and updating.
* TLS slots are not in any way architecture-specific; we do not even
have a mechanism by which they could be made so at present.
Thus, the initialization of them can be moved to common code, and
out of the per-architecture implementations.
* When dealing with a fork()ed thread, it will already have a TLS array
with values set in it. Therefore, do not overwrite the whole array,
but instead only update the specific values which have changed on fork.
This fixes at least part of #17896.
|