Thread Local Storage - Revision history

Kynex7510: Fix sizes

2025-11-25T22:45:37Z

Fix sizes

← Older revision		Revision as of 01:45, 26 November 2025
Line 18:		Line 18:
	\|-		\|-
	\| 0x40		\| 0x40
	\| ~~0x44~~		\| 0x04
	\| Exception handler return address		\| Exception handler return address
	\|-		\|-
	\| 0x44		\| 0x44
	\| ~~0x48~~		\| 0x04
	\| Exception handler SP control (1 = use aligned SP, other = use arbitrary memory, must be mapped & RW)		\| Exception handler SP control (1 = use aligned SP, other = use arbitrary memory, must be mapped & RW)
	\|-		\|-
	\| 0x48		\| 0x48
	\| ~~0x4C~~		\| 0x04
	\| Exception handler [[ERR:Throw#Exception\|context]] control (0 = use SP control memory, 1 = use aligned SP, other = use arbitrary memory, must be mapped & RW)		\| Exception handler [[ERR:Throw#Exception\|context]] control (0 = use SP control memory, 1 = use aligned SP, other = use arbitrary memory, must be mapped & RW)
	\|-		\|-
	\| 0x4C		\| 0x4C
	\| ~~0x80~~		\| 0x34
	\| Undefined		\| Undefined
	\|-		\|-

Kynex7510: Document exception handler fields

2024-11-01T21:29:31Z

Document exception handler fields

@@ Line 13: / Line 13: @@
 !  Description
 |-
-| 0
+| 0x00
 | 0x80
-| Undefined, can be used by application for any purpose.
+| Undefined
 |-
 | 0x80

Neobrain: Couldn't find this info anywhere. If it was already somewhere else, at least it's discoverable now :p

2016-03-20T12:13:13Z

Couldn't find this info anywhere. If it was already somewhere else, at least it's discoverable now :p

← Older revision		Revision as of 15:13, 20 March 2016
Line 23:		Line 23:
	\| 0x180		\| 0x180
	\| 0x80		\| 0x80
	\| IPC static buffers		\| IPC static buffers: 16 pairs of a [[IPC\|static buffer translation descriptor]] (specifying the buffer size) and a buffer pointer
	\|}		\|}

Bond697 at 01:30, 3 February 2016

2016-02-03T00:30:19Z

← Older revision		Revision as of 03:30, 3 February 2016
Line 1:		Line 1:
	Each thread is given a 0x200-byte thread-local-storage block by the kernel. It is used during [[IPC_Command_Structure\|IPC communications]].		Each thread is given a 0x200-byte thread-local-storage block by the kernel. It is used during [[IPC_Command_Structure\|IPC communications]]. Each [[KProcess]] has a linked list of [[KThreadLocalPage]] objects and each object has a pointer to a page(0x1000 bytes) of FCRAM, which is used for up to 8 thread-local-storage blocks. The [[KThreadLocalPage]] is used to track which thread-local-storage blocks are used so it can allocate new ones as new threads are created.

	A pointer to the thread-local-storage can be read using the ARM instruction:		A pointer to the thread-local-storage can be read using the ARM instruction:

Plutooo at 21:35, 3 September 2014

2014-09-03T19:35:43Z

← Older revision		Revision as of 23:35, 3 September 2014
Line 1:		Line 1:
	Each thread is given a 0x200-byte thread-local-storage block by the kernel. It is used during [[IPC_Command_Structure\|IPC communications]].		Each thread is given a 0x200-byte thread-local-storage block by the kernel. It is used during [[IPC_Command_Structure\|IPC communications]].

			A pointer to the thread-local-storage can be read using the ARM instruction:
			mrc 15, 0, rX, cr13, cr0, 3

			Every application has RW access to its thread-local-storage.

			The kernel requires the application to put IPC parameters and IPC static buffers inside the thread-local-storage:
	{\| class="wikitable" border="1"		{\| class="wikitable" border="1"
	\|-		\|-

Plutooo: Created page with "Each thread is given a 0x200-byte thread-local-storage block by the kernel. It is used during IPC communications. {| class="wikitable" border="1" |- ! ..."

2014-09-03T19:30:09Z

Created page with "Each thread is given a 0x200-byte thread-local-storage block by the kernel. It is used during IPC communications. {| class="wikitable" border="1" |- ! ..."

New page

Each thread is given a 0x200-byte thread-local-storage block by the kernel. It is used during [[IPC_Command_Structure|IPC communications]].

{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0
| 0x80
| Undefined, can be used by application for any purpose.
|-
| 0x80
| 0x100
| IPC command with parameters
|-
| 0x180
| 0x80
| IPC static buffers
|}