T-Kernel Specification (1.B0.02)

More documents

Recommendations

Info

132 CHAPTER 4. T-KERNEL/OS FUNCTIONS tk cal por Call Port for Rendezvous [C Language Interface] INT rmsgsz = tk_cal_por ( ID porid, UINT calptn, VP msg, INT cmsgsz, TMO tmout ) ; [Parameters] ID porid Rendezvous port ID UINT calptn Call bit pattern (indicating conditions of the caller) VP msg Message packet address INT cmsgsz Call message size (in bytes) TMO tmout Timeout designation [Return Parameters] INT rmsgsz Reply message size (in bytes) or Error Code [Error Codes] E OK E ID E NOEXS E PAR E DLT E RLWAI E DISWAI E TMOUT E CTX Normal completion Invalid ID number (porid is invalid or cannot be used) Object does not exist (the rendezvous port designated in porid does not exist) Parameter error ( cmsgsz < 0, cmsgsz > maxcmsz, calptn = 0, value that cannot be used in msg, tmout ≤ (−2) ) The object being waited for was deleted (the rendezvous port was deleted while waiting) Wait state released (tk rel wai received in wait state) Wait released by wait disabled state Polling failed or timeout Context error (issued from task-independent portion or in dispatch disabled state) [Description] Issues a rendezvous call for a rendezvous port. The specific operation of tk cal por is as follows. A rendezvous is established if there is a task waiting to accept a rendezvous at the port designated in porid and rendezvous conditions between that task and the task issuing this call overlap. In this case, the task waiting to accept the rendezvous enters READY state while the state of the task issuing tk cal por is WAIT for rendezvous completion. The task waiting for rendezvous completion is released from WAIT state when the other (accepting) task executes tk rpl rdv. The tk cal por system call completes at this time. If there is no task waiting to accept a rendezvous at the port designated in porid, or if there is a task but conditions for establishing a rendezvous are not satisfied, the task issuing tk cal por is placed at the Copyright c○ 2002, 2003 by T-Engine Forum T-Kernel 1.B0.02
4.5. EXTENDED SYNCHRONIZATION AND COMMUNICATION FUNCTIONS 133 end of the call queue of that port and enters WAIT state on rendezvous call. The order of tasks in the call queue is either FIFO or priority order, depending on the designation made when calling tk cre por. The decision on rendezvous establishment is made by checking conditions in the bit patterns acpptn of the accepting task and calptn of the calling task. A rendezvous is established if the bitwise logical AND of these two bit patterns is not 0. Parameter error E PAR is returned if calptn is 0, since no rendezvous can be established in that case. When a rendezvous is established, the calling task can send a message (a call message) to the accepting task. The size of the call message is designated in cmsgsz. In this operation cmsgsz bytes starting at address msg as designated by the calling task when calling tk cal por are copied to address msg as designated by the accepting task when calling tk acp por. Similarly, when the rendezvous completes, the accepting task may send a message (reply message) to the calling task. In this operation, the contents of a reply message designated by the accepting task when calling tk rpl rdv are copied to address msg as designated by the calling task when calling tk cal por. The size of the reply message rmsgsz is set in a tk cal por return parameter. The original contents of the message area passed in msg by tk cal por end up being overwritten by the reply message received when tk rpl rdv executes. Note that it is possible message contents will be destroyed when a rendezvous is forwarded, since an area no larger than maxrmsz starting from the address msg as designated with tk cal por is used as a buffer. It is therefore necessary to reserve a memory space of at least maxrmsz starting from msg, regardless of the expected size of the reply message, whenever there is any possibility that a rendezvous requested by tk cal por might be forwarded (See the description of tk fwd por for details). Error code E PAR is returned when cmsgsz exceeds the size maxcmsz designated with tk cre por. This error checking is made before a task enters WAIT state on rendezvous call; and if error is detected, the task executing tk cal por does not enter WAIT state. A maximum wait time (timeout) can be set in tmout. If the tmout time elapses before the wait release condition is met (rendezvous is not established), the system call terminates, returning timeout error code E TMOUT. Only positive values can be set in tmout. The time base for tmout (time unit) is the same as that for system time (= 1 ms). When TMO POL = 0 is set in tmout, this means 0 was designated as the timeout value, and E TMOUT is returned without entering WAIT state if there is no task waiting on a rendezvous at the rendezvous port, or if the rendezvous conditions are not met. When TMO FEVR = (−1) is set in tmout, this means infinity was designated as the timeout value, and the task continues to wait for a rendezvous to be established without timing out. In any case, the tmout designation indicates the time allowed for a rendezvous to be established, and does not apply to the time from rendezvous establishment to rendezvous completion. 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:
4.4. SYNCHRONIZATION AND COMMUNICAT
Page 105 and 106: 4.4. SYNCHRONIZATION AND COMMUNICAT
Page 131 and 132: 4.5. EXTENDED SYNCHRONIZATION AND C
Page 155: 4.5. EXTENDED SYNCHRONIZATION AND C
Page 171 and 172: 4.6. MEMORY POOL MANAGEMENT FUNCTIO
Page 187 and 188: 4.7. TIME MANAGEMENT FUNCTIONS 163
Page 207 and 208:
4.7. TIME MANAGEMENT FUNCTIONS 183
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 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
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 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
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)

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

Delete template?

Save as template?