KScheduler - Revision history

TuxSH at 00:11, 8 December 2016

2016-12-07T23:11:23Z

← Older revision		Revision as of 02:11, 8 December 2016
Line 60:		Line 60:
	\|-		\|-
	\| 0x20		\| 0x20
	\| ~~u32~~		\| [[KThread\|KThreadLinkedList]]
	~~\| Unknown~~		\| Linked list of threads managed by this KScheduler instance
	\|-
	~~\| 0x24~~
	\| ~~u32~~
	\| ~~Unknown/unused~~
	\|-		\|-
	\| 0x28		\| 0x28
Line 71:		Line 67:
	\| List of KThread pair structs by priority		\| List of KThread pair structs by priority
	\|}		\|}



	~~ThreadSchedulePrioList struct:~~
	~~{\| class="wikitable" border="1"~~
	\|-
	~~! Offset~~
	~~! Type~~
	~~! Description~~
	\|-
	~~\| 0x0~~
	\| KThread*
	~~\| First~~
	\|-
	~~\| 0x4~~
	\| KThread*
	~~\| Last~~
	\|}


	There is 1 KScheduler object per core.		There is 1 KScheduler object per core.
Line 96:		Line 73:
	The second virtual method is stubbed.		The second virtual method is stubbed.

			Each priority of KThread has an associated linked list of KThreads object pointers below the KScheduler object. Each pair of pointers makes up 1 entry in that core's Scheduler for their priority.
	~~ThreadSchedulePrioList info:~~

	Each priority of KThread has ~~a pair~~ of ~~KThread~~ object pointers below the KScheduler object. Each pair of pointers makes up 1 entry in that core's Scheduler for their priority. ~~The first KThread in the entry is the first KThread in the linked list and the second is the last KThread in the linked list of KThreads in the scheduler that have the same priority.~~


	Priority bit fields:		Priority bit fields:

	Each bit field goes from the most significant bit to the least significant bit, high priority to low priority. This means, for example, that bit 31 in the high priority bit field is for priority 0 and bit 0 is for priority 31. These fields are set when a KThread with the corresponding priority is added for scheduling and are cleared when the last KThread in the linked list for a given priority is removed from the scheduler.		Each bit field goes from the most significant bit to the least significant bit, high priority to low priority. This means, for example, that bit 31 in the high priority bit field is for priority 0 and bit 0 is for priority 31. These fields are set when a KThread with the corresponding priority is added for scheduling and are cleared when the last KThread in the linked list for a given priority is removed from the scheduler.

TuxSH at 00:33, 5 December 2016

2016-12-04T23:33:47Z

← Older revision		Revision as of 02:33, 5 December 2016
Line 1:		Line 1:
	[[Category:Kernel ~~objects~~]]		[[Category:Kernel interrupt events]]

	class [[KScheduler]] extends [[KSchedulableInterruptEvent]];		class [[KScheduler]] extends [[KSchedulableInterruptEvent]];

Yuriks at 02:43, 4 December 2016

2016-12-04T01:43:48Z

← Older revision		Revision as of 04:43, 4 December 2016
Line 57:		Line 57:
	\| 0x1C		\| 0x1C
	\| KThread*		\| KThread*
	\| Scheduler thread		\| Scheduler's idle thread (runs when no other runnable thread is available)
	\|-		\|-
	\| 0x20		\| 0x20

TuxSH at 20:28, 3 December 2016

2016-12-03T19:28:04Z

← Older revision		Revision as of 22:28, 3 December 2016
Line 1:		Line 1:
	[[Category:Kernel objects]]		[[Category:Kernel objects]]

			class [[KScheduler]] extends [[KSchedulableInterruptEvent]];

	Size : 0x228 bytes		Size : 0x228 bytes


	{\| class="wikitable" border="1"		{\| class="wikitable" border="1"
Line 11:		Line 12:
	\|-		\|-
	\| 0x0		\| 0x0
	\| ~~u32~~		\| void **
	\| Pointer to vtable		\| Pointer to vtable
	\|-		\|-
	\| 0x4		\| 0x4
	\| ~~u32~~		\| [[KSynchronizationObject]] *
	\| Unused~~, may have been for reference count~~		\| Inherited field. Unused.
	\|-		\|-
	\| 0x8		\| 0x8
Line 91:		Line 92:

	There is 1 KScheduler object per core.		There is 1 KScheduler object per core.

			KScheduler instances are mapped to SGI #8. The interrupt handler/callback returns 1, which triggers a post-interrupt rescheduling and context switch (like all the other handlers not returning NULL), but does nothing else in particular.
			The second virtual method is stubbed.

Bond697 at 22:14, 18 February 2016

2016-02-18T21:14:26Z

← Older revision		Revision as of 00:14, 19 February 2016
Line 20:		Line 20:
	\| 0x8		\| 0x8
	\| u32		\| u32
	\| Count for thread ~~switches~~ - this is only added to if a context switch function runs but exits because the scheduler is locked by another thread.		\| Count for thread switch attempts - this is only added to if a context switch function runs but exits because the scheduler is locked by another thread.
	\|-		\|-
	\| 0xC		\| 0xC

Bond697 at 06:53, 23 March 2015

2015-03-23T05:53:40Z

← Older revision		Revision as of 08:53, 23 March 2015
Line 52:		Line 52:
	\| 0x18		\| 0x18
	\| u32		\| u32
	\| Bit field for low priority threads in KScheduler(32-63)\		\| Bit field for low priority threads in KScheduler(32-63)
	\|-		\|-
	\| 0x1C		\| 0x1C

Bond697 at 03:22, 19 March 2015

2015-03-19T02:22:48Z

@@ Line 65: / Line 65: @@
 | u32
 | Unknown/unused
 |}
 There is 1 KScheduler object per core.
 Each priority of KThread has a pair of KThread object pointers below the KScheduler object.  Each pair of pointers makes up 1 entry in that core's Scheduler for their priority.  The first KThread in the entry is the first KThread in the linked list and the second is the last KThread in the linked list of KThreads in the scheduler that have the same priority.

Bond697 at 03:18, 19 March 2015

2015-03-19T02:18:28Z

@@ Line 45: / Line 45: @@
 | s16
 | Count of threads currently being managed by this scheduler object
 |}
 There is 1 KScheduler object per core.

Bond697 at 17:46, 18 March 2015

2015-03-18T16:46:39Z

← Older revision		Revision as of 19:46, 18 March 2015
Line 2:		Line 2:

	Size : 0x228 bytes		Size : 0x228 bytes


	{\| class="wikitable" border="1"		{\| class="wikitable" border="1"
Line 15:		Line 16:
	\| 0x4		\| 0x4
	\| u32		\| u32
	\| Unused		\| Unused, may have been for reference count
	\|-		\|-
	\| 0x8		\| 0x8
Line 36:		Line 37:
	\| bool		\| bool
	\| Post-interrupt rescheduling needed		\| Post-interrupt rescheduling needed
			\|-
			\| 0x10
			\| s16
			\| Scheduler core number
			\|-
			\| 0x12
			\| s16
			\| Count of threads currently being managed by this scheduler object
	\|}		\|}


			There is 1 KScheduler object per core.

Bond697 at 17:40, 18 March 2015

2015-03-18T16:40:52Z

@@ Line 20: / Line 20: @@
 | u32
 | Count for thread switches - this is only added to if a context switch function runs but exits because the scheduler is locked by another thread.
 |}