INtimeÂ® 3.1 Software - tenAsys

More documents

Recommendations

Info

INtime <strong>3.1</strong> <strong>Software</strong> • Asleep: The thread waits for an object or one of a set of objects to be signaled, or for a specific timeout, or both. While in this state, the thread will never be running. • Suspended: The thread is waiting for a resume operation. More than one suspend can be done, and each such suspend must be undone by a resume. While in this state, the thread will never be running. • Asleep suspended: While in the asleep state, the thread was suspended. Both the suspend state and the asleep state must be undone before the thread becomes ready again. A thread has a stack for calling functions and storing local variables and parameters. The stack must be big enough to contain all necessary data; when it overflows, it is not extended but the hardware exception EH_STACK_FAULT occurs. A thread can refer to itself by a so-called pseudo handle, which is not a fixed value, but must be obtained by the GetCurrentThread function. A pseudo handle can only be used within the owning process, and it cannot be closed (it is implicitly closed when the thread terminates). Waiting for a thread to be signaled means waiting until the thread has terminated. Thread handling functions include: iwin32 calls iwin32x calls CreateThread or RtCreate Thread – ExitThread or RtExitThread – GetCurrentThread – GetCurrentThreadId – GetExitCodeThread – GetLastError or RtGetLastError – GetThreadPriority or RtGetThreadPriority – RtGetThreadTimeQuantum – OpenThread – ResumeThread or RtResumeThread – SetLastError or RtSetLastError – SetThreadPriority or RtSetThreadPriority – RtSetThreadTimeQuantum – Sleep or RtSleep – RtSleepFt or RtSleepFt RtSleepFt SuspendThread or RtSuspendThread – TerminateThread or RtTerminateThread – WaitForMultipleObjects or RtWaitForMultipleObjects RtWaitForMultipleObjects WaitForSingleObject or RtWaitForSingleObject RtWaitForSingleObjects 144
Appendix B: The iwin32 subsystem Mutexes A mutex is an object for getting exclusive access to a resource used by more than one thread, possibly in different processes. When a thread attempts to get ownership of a mutex and that mutex is free, ownership is given to that thread; until the thread releases ownership, no other thread can own the same mutex. A thread can own the same mutex more than once, in which case it must release the mutex the same number of times. When a thread with INtime priority Pw wishes to own a mutex and that mutex is already owned by another thread with priority Po, then if Pw is better than Po, the priority of the owning thread is changed to Pw until it releases all mutexes it owns. This avoids the infamous priority inversion, as described in Priority inversions on page 37. Termination of a thread that owns one or more mutexes causes all threads waiting for such mutexes to be woken up with a WAIT_ABANDONED exception. Deleting a mutex causes all threads waiting for that mutex to be woken up with an ERROR_INVALID_HANDLE error code. Mutex manipulation functions are: iwin32 calls CreateMutex or RtCreateMutex OpenMutex or RtOpenMutex ReleaseMutex or RtReleaseMutex WaitForMultipleObjects or RtWaitForMultipleObjects WaitForSingleObject or RtWaitForSingleObject iwin32x calls RtCreateMutex RtOpenMutex RtReleaseMutex RtWaitForMultipleObjects RtWaitForSingleObjects Critical section A critical section is a mutex that has no name; it can therefore only be used in the process that creates it. A critical section is identified by a CRITICAL_SECTION structure, which in turn contains the handle of the mutex. For more details see mutexes. Functions for critical sections include: iwin32 calls DeleteCriticalSection EnterCriticalSection InitializeCriticalSection LeaveCriticalSection TryEnterCriticalSection iwin32x calls Part of Win32 Part of Win32 Part of Win32 Part of Win32 Part of Win32 145
Page 1 and 2:
U S E R ’ S M A N U A L INtime ®
Page 3 and 4:
Before you begin This guide describ
Page 5 and 6:
Before you begin Glossary Notationa
Page 7 and 8:
Before you begin • Within source
Page 9 and 10:
Contents Part I Chapter 1 Chapter 2
Page 11 and 12:
Contents Part II Chapter 6 Chapter
Page 13 and 14:
Contents Part III Appendix A Append
Page 15 and 16:
Contents NTX DLLs..................
Page 17 and 18:
I Introducing INtime software This
Page 19 and 20:
1 Overview INtime software extends
Page 21 and 22:
Chapter 1: Overview Considerations
Page 23 and 24:
Chapter 1: Overview Developing an I
Page 25 and 26:
Chapter 1: Overview INtime software
Page 27 and 28:
Chapter 1: Overview • INtime Grap
Page 29 and 30:
Chapter 1: Overview • Remote conf
Page 31 and 32:
2 Understanding INtime software arc
Page 33 and 34:
Chapter 2: Understanding INtime sof
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
3 About INtime software’s RT kern
Page 47 and 48:
Chapter 3: About INtime software’
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
4 About RT programming This chapter
Page 57 and 58:
Chapter 4: About RT programming Pre
Page 59 and 60:
Chapter 4: About RT programming whe
Page 61 and 62:
Chapter 4: About RT programming Fig
Page 63 and 64:
Chapter 4: About RT programming Syn
Page 65 and 66:
Chapter 4: About RT programming The
Page 67 and 68:
Chapter 4: About RT programming Exc
Page 69 and 70:
Chapter 4: About RT programming Str
Page 71 and 72:
5 Designing RT applications This ch
Page 73 and 74:
Chapter 5: Designing RT application
Page 75 and 76:
Chapter 5: Designing RT application
Page 77 and 78:
II Using INtime software This part
Page 79 and 80:
6 Installation This chapter explain
Page 81 and 82:
Chapter 6: Installation 5. Select o
Page 83 and 84:
7 Configuration INtime software pro
Page 85 and 86:
Chapter 7: Configuration Tab Local
Page 87 and 88:
Chapter 7: Configuration Configurin
Page 89 and 90:
Chapter 7: Configuration Setting th
Page 91 and 92:
8 Preparing an RT node This chapter
Page 93 and 94:
Chapter 8: Preparing an RT node Bui
Page 95 and 96:
Chapter 8: Preparing an RT node 4.
Page 97 and 98:
Chapter 8: Preparing an RT node Fir
Page 99 and 100:
9 Operation This chapter describes
Page 101 and 102:
Chapter 9: Operation • INtime too
Page 103 and 104:
10 INtime application development T
Page 105 and 106:
Chapter 10: INtime application deve
Page 107 and 108:
Chapter 10: INtime application deve
Page 109 and 110: Chapter 10: INtime application deve
Page 125 and 126: III Appendices The appendices inclu
Page 127 and 128: A INtime software system calls This
Page 129 and 130: Appendix A: INtime software system
Page 157 and 158: B The iwin32 subsystem This appendi
Page 159: Appendix B: The iwin32 subsystem A
Page 163 and 164: Appendix B: The iwin32 subsystem Sh
Page 165 and 166: Appendix B: The iwin32 subsystem Us
Page 167 and 168: Appendix B: The iwin32 subsystem Pr
Page 169 and 170: C INtime directory structure This a
Page 171 and 172: D INtime software components This a
Page 173 and 174: Appendix D: INtime software compone
Page 189 and 190: E Visual Studio .NET debugging for
Page 191 and 192: Appendix E: Visual Studio .NET debu
Page 193 and 194: F Adding INtime software to an XP E
Page 195 and 196: G Troubleshooting This appendix lis
Page 197 and 198: Appendix G: Troubleshooting Table G
Page 199 and 200: Appendix G: Troubleshooting Table G
Page 201 and 202: Glossary application loader asynchr
Page 203 and 204: Glossary memory area memory pool me
Page 205 and 206: Index A B C D E F G H I J K L M N O
Page 207 and 208: A B C D E F G H I J K L M N O P Q R
Page 209 and 210: A B C D E F G H I J K L M N O P Q R
Page 211 and 212:
A B C D E F G H I J K L M N O P Q R
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
show all

INtimeÂ® 3.1 Software - tenAsys

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

Delete template?

Save as template?