T-Kernel Specification (1.B0.02)

More documents

Recommendations

Info

134 CHAPTER 4. T-KERNEL/OS FUNCTIONS tk acp por Accept Port for Rendezvous [C Language Interface] INT cmsgsz = tk_acp_por ( ID porid, UINT acpptn, RNO *p_rdvno, VP msg, TMO tmout ) ; [Parameters] ID porid Rendezvous port ID UINT acpptn Accept bit pattern (indicating conditions for acceptance) VP msg Message packet address TMO tmout Timeout designation [Return Parameters] ER ercd Error code RNO rdvno Rendezvous number INT cmsgsz Call message size (in bytes) [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, or porid is a rendezvous port of another node) Object does not exist (the rendezvous port designated in porid does not exist) Parameter error (acpptn = 0, value that cannot be used in msg, or 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] Accepts a rendezvous on a rendezvous port. The specific operation of tk acp por is as follows. A rendezvous is established if there is a task queued for a rendezvous call at the port designated in porid and if rendezvous conditions of that task and the task issuing this call overlap. In this case, the task queued for a rendezvous call is removed from the queue, and its state changes from WAIT on rendezvous call to WAIT for rendezvous completion. The task issuing tk acp por continues executing. If there is no task waiting to call 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 acp por will enter WAIT state on rendezvous acceptance for that port. No error results if there is already another task in WAIT state on rendezvous acceptance at this time; the task issuing tk acp por is placed in the Copyright c○ 2002, 2003 by T-Engine Forum T-Kernel 1.B0.02
4.5. EXTENDED SYNCHRONIZATION AND COMMUNICATION FUNCTIONS 135 accept queue. It is possible to conduct multiple rendezvous operations on the same port at the same time. Accordingly, no error results even if the next rendezvous is carried out while another task is still conducting a rendezvous (before tk rpl rdv is called for a previously established rendezvous) at the port designated in porid. 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. If the first task does not satisfy these conditions, each subsequent task in the call queue is checked in succession. If calptn and acpptn are assigned the same non-zero value, rendezvous is established unconditionally. Parameter error E PAR is returned if acpptn is 0, since no rendezvous can be established in that case. All processing before a rendezvous is established is fully symmetrical on the calling and accepting ends. When a rendezvous is established, the calling task can send a message (a call message) to the accepting task. The contents of the message designated by the calling task are copied to an area starting from msg designated by the accepting task when tk acp por is called. The call message size cmsgsz is passed in a return parameter of tk acp por. A task accepting rendezvous can establish more than one rendezvous at a time. That is, a task that has accepted one rendezvous using tk acp por may execute tk acp por again before executing tk rpl rdv on the first rendezvous. The port designated for the second tk acp por call at this time may be the same port as the first rendezvous or a different one. It is even possible for a task already conducting a rendezvous on a given port to execute tk acp por again on the same port and conduct multiple rendezvous on the same port at the same time. Of course, the calling tasks will be different in each case. The return parameter rdvno passed by tk acp por is information used to distinguish different rendezvous when more than one has been established at a given time. It is used as a return parameter by tk rpl rdv when a rendezvous completes. It is also passed as a parameter to tk fwd por when forwarding a rendezvous. Although the exact contents of rdvno are implementation-dependent, it is expected to include information designating the calling task on the other end of the rendezvous. 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 for a rendezvous call 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. select when condition_A accept entry_A do ... end; or when condition_B accept entry_B do ... end; or when condition_C accept entry_C do ... end; end select; Figure 4.6: Sample ADA-like Program Using select Statement 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: 4.4. SYNCHRONIZATION AND COMMUNICAT
Page 131 and 132: 4.5. EXTENDED SYNCHRONIZATION AND C
Page 157: 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 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?