T-Kernel Specification (1.B0.02)

More documents

Recommendations

Info

242 CHAPTER 5. T-KERNEL/SM only the wait is aborted (wait release), not the requested processing itself. When a wait for multiple requests is aborted (wait release), E ABORT is passed in the waitfn return code. During a wait for request completion, an abort request may be set in the abort parameter of a request packet. In such a case, if it is a single request, the request abort processing must be performed. If the wait is for multiple requests it is also preferable that abort processing be executed, but it is also possible to ignore the abort flag. When abort occurs, the important thing is to return from waitfn as quickly as possible. processing will end soon anyway without aborting, it is not necessary to abort. As a rule, E ABORT is returned in the request packet error parameter when processing is aborted; but a different error code may be returned as appropriate based on the device properties. It is also permissible to return E OK on the basis that the processing right up to the abort is valid. If processing completes normally to the end, E OK is returned even if there was an abort request. • Abort Function: ER abortfn( ID tskid, T_DEVREQ *devreq, INT nreq, VP exinf ) tskid devreq nreq exinf return code Task ID of the task executing execfn or waitfn Request packet list Request packet count Extended information set at device registration Error The function abortfn causes execfn or waitfn to return promptly when the designated request is being executed. Normally this means the request being processed is aborted. If, however, the processing can be completed soon without aborting, it may not have to be aborted. The important thing is to return as quickly as possible from execfn or waitfn. tskid indicates the task executing the request designated in devreq. In other words, it is the task executing execfn or waitfn. devreq and nreq are the same as the parameters that were passed to execfn or waitfn. In the case of execfn, nreq is always 1. abortfn is called by a different task from the one executing execfn or waitfn. Since both tasks run concurrently, mutual exclusion control must be performed as necessary. It is possible that the abortfn function will be called immediately before calling execfn or waitfn, or during return from these functions. Measures must be taken to ensure proper operation in such cases. Before abortfn is called, the abort flag in the request packet whose processing is to be aborted is set to TRUE, enabling execfn or waitfn to know whether there is going to be an abort request. Note also that abortfn can make use of tk dis wai for any object. When waitfn is executing for multiple requests (nreq > 1), this is treated as a special case differing as follows from other cases. – Only the completion wait is aborted (wait release), not the requested processing. – The abort flag is not set in the request packet (remains as abort = FALSE). Aborting a request when execfn and waitfn are not executing is done not by calling abortfn but by setting the request packet abort flag. If execfn is called when the abort flag is set, the request is not accepted. If waitfn is called, abort processing is the same as that when abortfn is called. If a request for which processing was started by execfn is aborted before waitfn was called to wait for its completion, the completion of the aborted processing is notified when waitfn is called. Even though processing was aborted, the request itself is not discarded until its completion has been confirmed by waitfn. If Copyright c○ 2002, 2003 by T-Engine Forum T-Kernel 1.B0.02
5.3. DEVICE MANAGEMENT FUNCTIONS 243 abortfn starts abort processing only, returning promptly without waiting for the abort to complete. abortfn is called in the following cases. – When a break function is executing after a task exception and the task that raised the exception requests abort processing, abortfn is used to abort the request being processed by that task. – When a device is being closed by tk cls dev and by subsystem cleanup processing, and a device descriptor was processing a request, abortfn is used to abort the request being processed by that device descriptor. • Event Handling Function: INT eventfn( INT evttyp, VP evtinf, VP exinf ) evttyp evtinf exinf return code Driver request event type Information for each event type Extended information set at device registration Return code defined for each event type or error The following driver request event types are defined. Those with positive values are called by tk evt dev, and those with negative values are called inside device management. #define TDV_SUSPEND (-1) /* suspend */ #define TDV_RESUME (-2) /* resume */ #define TDV_CARDEVT 1 /* PC Card event (see Card Manager */ #define TDV_USBEVT 2 /* USB event (see USB Manager) */ p The processing performed by an event function is defined for each event type. Suspend and resume processing are discussed later below. When a device event is called by tk evt dev, the eventfn return code is set transparently as the tk evt dev return code. Requests to event functions must be accepted even if another request is processing and must be processed as quickly as possible. 5.3.5 Attribute Data Attribute data is classified broadly into the following three kinds of data. • Common attributes Attributes defined in common for all devices (device drivers). • Device kind attributes Attributes defined in common for devices (device drivers) of the same kind. • Device-specific attributes Attributes defined independently for each device (device driver). For the device kind attributes and device-specific attributes, see the specifications for each device. Only the common attributes are defined here. Common attributes are assigned attribute data numbers in the range from −1 to −99. While common attribute data numbers are the same for all devices, not all devices necessarily support all common attributes. If an unsupported data number is designated, error code E PAR is returned. 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:
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 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 265: 5.3. DEVICE MANAGEMENT FUNCTIONS 24
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 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 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?