T-Kernel Specification (1.B0.02)

More documents

Recommendations

Info

256 CHAPTER 5. T-KERNEL/SM 5.8 Subsystem and Device Driver Starting Entry routines like the following are defined for subsystems and device drivers. ER main( INT ac, UB *av[] ) { if ( ac >= 0 ) { /* Subsystem/device driver start processing */ } else { /* Subsystem/device driver termination processing */ } return ercd; } This entry routine simply performs startup processing or termination processing for a subsystem or device driver and does not provide any actual service. It must return to its caller as soon as the startup processing or termination processing is performed. An entry routine must perform its processing as quickly as possible and return to its caller. An entry routine is called by the task which belongs to the system resource group at the time of normal system startup or shutdown, and runs in the context of the OS start processing task or termination processing task (protection level 0). In some OS implementations, it may run as a quasi-task portion. In a system that supports dynamic loading of subsystems and device drivers, it may be called at other times besides system startup and shutdown. When there are multiple subsystems and device drivers, entry routines are called one at a time for each, at system startup and shutdown. In no case are multiple entry routines called by different tasks at the same time. Accordingly, if subsystem or device driver initialization needs to be performed in a certain order, this order can be maintained by completing all necessary processing before returning from an entry routine. The entry routine function name is normally main, but any other name may be used if, for example, main cannot be used because of linking with the OS. The methods of registering entry routines with the OS, designating parameters, and designating the order in which entry routines are called are all dependent on the OS implementation. • Startup processing ac Number of parameters (≥ 0) av Parameters (string) return code Error A value of ac ≥ 0 indicates startup processing. After performing the subsystem or device driver initialization, it registers the subsystem or device driver. Passing of a negative value (error) as the return code means the startup processing failed. Depending on the OS implementation, the subsystem or device driver may be deleted from memory, so error must not be returned while the subsystem or device driver is in registered state. The registration must first be erased before returning error. Allocated resources must also be released. They are not released automatically. The parameters ac and av are the same as the parameters passed to the standard C language main() function, with ac indicating the number of parameters and av indicating a parameter string as an array of ac + 1 pointers. The array termination (av[ac]) is NULL. av[0] is the name of the subsystem or device driver. Generally this is the file name of the subsystem or device driver, but the kind of name in which it is stored is implementation-dependent. It is also possible to have no name (blank string ""). Copyright c○ 2002, 2003 by T-Engine Forum T-<strong>Kernel</strong> <strong>1.B0.02</strong>
5.8. SUBSYSTEM AND DEVICE DRIVER STARTING 257 Parameters after av[1] are defined separately for each subsystem and device driver. After exit from the entry routine, the character string space designated by av is deleted, so parameters must be saved to a different location as needed. • Termination processing ac av return code −1 NULL Error A value of ac < 0 indicates termination processing. After deleting the subsystem or device driver registration, the entry routine releases allocated resources. If an error occurs during termination processing, the processing must not be aborted but must be completed to the extent possible. If some of the processing could not be completed normally, error is passed in the return code. The behavior if termination processing is called while requests to the subsystem or device driver are being processed is dependent on the subsystem or device driver implementation. Generally termination processing is called at system shutdown and requests are not issued during process-
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:
Page 185 and 186:
Page 187 and 188:
4.7. TIME MANAGEMENT FUNCTIONS 163
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
4.8. INTERRUPT MANAGEMENT FUNCTIONS
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
4.9. SYSTEM MANAGEMENT FUNCTIONS 19
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230: 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 273 and 274: 5.4. INTERRUPT MANAGEMENT FUNCTIONS
Page 275 and 276: 5.5. IO PORT ACCESS SUPPORT FUNCTIO
Page 277 and 278: 5.7. SYSTEM CONFIGURATION INFORMATI
Page 279: 5.7. SYSTEM CONFIGURATION INFORMATI
Page 284 and 285: 260 CHAPTER 6. T-KERNEL/DS FUNCTION
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)

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?