T-Kernel Specification (1.B0.02)

More documents

Recommendations

Info

210 CHAPTER 4. T-KERNEL/OS FUNCTIONS [Additional Notes] Extended SVC handlers as well as break functions, startup functions, cleanup functions and event handling functions all have the equivalent of the TA HLNG attribute only. There is no means of designating the TA ASM attribute. Prior to initialization of a resource control block by a startup function, and after resource release by a cleanup function, the behavior if an extended SVC is called by a task belonging to that resource group is dependent on the subsystem implementation. The OS does not make any attempt to prevent this kind of call. Basically it is necessary to avoid calling an extended SVC before calling a startup function and after calling a cleanup function. There may be cases where, for some reason or other, a break function, cleanup function or event handling function is called without first calling a startup function. These functions must execute normally even in such a case. A resource control block is cleared to 0 when it is first created and when cleanup processing is executed by tk cln ssy. Accordingly, even if it was not initialized properly by a startup function, the resource control block can still be assumed to have been cleared to 0. Copyright c○ 2002, 2003 by T-Engine Forum T-Kernel 1.B0.02
4.10. SUBSYSTEM MANAGEMENT FUNCTIONS 211 tk sta ssy tk cln ssy Call Startup Function of Sub-System Call Cleanup Function of Sub-System [C Language Interface] ER ercd = tk_sta_ssy ( ID ssid, ID resid, INT info ) ; ER ercd = tk_cln_ssy ( ID ssid, ID resid, INT info ) ; [Parameters] ID ssid Subsystem ID ID resid Resource ID INT info Any parameter [Return Parameters] ER ercd Error code [Error Codes] E OK E ID E NOEXS E CTX Normal completion Invalid ID number (ssid or resid is invalid or cannot be used) Object does not exist (the subsystem designated in ssid is not defined) Context error (issued from task-independent portion or in dispatch disabled state) [Description] Calls the startup function/cleanup function of the subsystem designated in ssid. A designation of ssid = 0 makes the system call applicable to all currently defined subsystems. In this case the startup/cleanup functions of each subsystem are called in sequence. tk sta ssy: Calls in order starting from the highest subsystem priority. tk cln ssy: Calls in order starting from the lowest subsystem priority. The order among subsystems having the same priority is not defined. If there are dependency relationships among different subsystems, the subsystem priority must therefore be set with those relationships in mind. If, for example, subsystem B uses functions in subsystem A, then the priority of subsystem A must be set higher than that of subsystem B. Even if these system calls are issued for a subsystem with no startup function or cleanup function defined, those functions are simply not called; no error results. If during startup/cleanup function execution a task exception is raised for the task that called tk sta ssy or tk cln ssy, the task exception is held until the startup/cleanup function completes its processing. Copyright c○ 2002, 2003 by T-Engine Forum T-Kernel 1.B0.02
Page 1 and 2:
T-Kernel Specification T-Kernel 1.B
Page 3 and 4:
Contents 1 T-Kernel Overview 1 1.1
Page 5 and 6:
CONTENTS v tk set flg (Set Event Fl
Page 7 and 8:
CONTENTS vii 5.2.2 Address Space Ch
Page 9 and 10:
CONTENTS ix td cal que (Reference Q
Page 11 and 12:
List of Figures 1.1 Position of T-K
Page 13 and 14:
List of Tables 2.1 State Transition
Page 15 and 16:
System Call Notation In the parts o
Page 17 and 18:
Index of T-Kernel/OS System Calls T
Page 19 and 20:
INDEX OF T-KERNEL/OS SYSTEM CALLS x
Page 21 and 22:
Index of T-Kernel/SM Extended SVC L
Page 23 and 24:
Index of T-Kernel/DS System Calls T
Page 25 and 26:
Chapter 1 T-Kernel Overview 1.1 Pos
Page 27 and 28:
1.2. SCALABILITY 3 • Middleware m
Page 29 and 30:
Chapter 2 Concepts Underlying the T
Page 31 and 32:
2.2. TASK STATES AND SCHEDULING RUL
Page 33 and 34:
2.2. TASK STATES AND SCHEDULING RUL
Page 35 and 36:
2.3. INTERRUPT HANDLING 11 preceden
Page 37 and 38:
2.5. SYSTEM STATES 13 Transient sta
Page 39 and 40:
2.7. MEMORY 15 which the upper and
Page 41 and 42:
Chapter 3 Common T-Kernel Specifica
Page 43 and 44:
3.2. SYSTEM CALLS 19 /* * Common co
Page 45 and 46:
3.2. SYSTEM CALLS 21 Ordinarily a f
Page 47 and 48:
3.3. HIGH-LEVEL LANGUAGE SUPPORT RO
Page 49 and 50:
Chapter 4 T-Kernel/OS Functions Thi
Page 51 and 52:
4.1. TASK MANAGEMENT FUNCTIONS 27 t
Page 53 and 54:
4.1. TASK MANAGEMENT FUNCTIONS 29 #
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
4.2. TASK-DEPENDENT SYNCHRONIZATION
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
4.3. TASK EXCEPTION HANDLING FUNCTI
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
4.4. SYNCHRONIZATION AND COMMUNICAT
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
4.5. EXTENDED SYNCHRONIZATION AND C
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
4.6. MEMORY POOL MANAGEMENT FUNCTIO
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184: 4.6. MEMORY POOL MANAGEMENT FUNCTIO
Page 185 and 186: 4.6. MEMORY POOL MANAGEMENT FUNCTIO
Page 187 and 188: 4.7. TIME MANAGEMENT FUNCTIONS 163
Page 209 and 210: 4.8. INTERRUPT MANAGEMENT FUNCTIONS
Page 215 and 216: 4.9. SYSTEM MANAGEMENT FUNCTIONS 19
Page 229 and 230: 4.10. SUBSYSTEM MANAGEMENT FUNCTION
Page 233: 4.10. SUBSYSTEM MANAGEMENT FUNCTION
Page 243 and 244: Chapter 5 T-Kernel/SM Details of th
Page 245 and 246: 5.1. SYSTEM MEMORY MANAGEMENT FUNCT
Page 247 and 248: 5.2. ADDRESS SPACE MANAGEMENT FUNCT
Page 249 and 250: 5.2. ADDRESS SPACE MANAGEMENT FUNCT
Page 251 and 252: 5.3. DEVICE MANAGEMENT FUNCTIONS 22
Page 275 and 276: 5.5. IO PORT ACCESS SUPPORT FUNCTIO
Page 277 and 278: 5.7. SYSTEM CONFIGURATION INFORMATI
Page 279 and 280: 5.7. SYSTEM CONFIGURATION INFORMATI
Page 281: 5.8. SUBSYSTEM AND DEVICE DRIVER ST
Page 284 and 285:
260 CHAPTER 6. T-KERNEL/DS FUNCTION
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
284 CHAPTER 7. REFERENCE INT tevptn
Page 310 and 311:
286 CHAPTER 7. REFERENCE ER ercd =
Page 312 and 313:
288 CHAPTER 7. REFERENCE INT ct = t
Page 314:
290 CHAPTER 7. REFERENCE E OACV ERC
show all

T-Kernel Specification (1.B0.02)

Create successful ePaper yourself

Delete template?

Save as template?