Difference between revisions of "IOP OS"
Hallowizer (talk | contribs) (→Toggling interrupts: confirmed that the IOS scheduler doesn't perfectly simulate disabling interrupts, but the ROS scheduler does) |
Hallowizer (talk | contribs) (named the modules that use this) |
||
Line 1: | Line 1: | ||
− | '''IOP OS''' is a set of functions in [[IOS]] | + | '''IOP OS''' is a set of functions in the NET and SSL modules in [[IOS]] that convert [[Revolution OS]] calls to IOS [[IOS/Syscalls|syscalls]]; for example, OSAlloc is implemented as a call to IOS_Alloc. |
== Toggling interrupts == | == Toggling interrupts == |
Revision as of 07:22, 22 June 2022
IOP OS is a set of functions in the NET and SSL modules in IOS that convert Revolution OS calls to IOS syscalls; for example, OSAlloc is implemented as a call to IOS_Alloc.
Toggling interrupts
Disabling interrupts is simulated by locking a mutex (but not an OSMutex
) implemented as a message queue and changing the current thread priority to 0x38 (higher than other threads in the process). While this does not completely prevent concurrent execution within the module, it is enough for most uses of OSDisableInterrupts
. Despite this, the design used may be a mistake when porting the code to IOS, since lower priority Revolution OS threads can starve from being blocked by higher priority threads, which would achieve this goal.
Threads
Threads are implemented as a proxy to IOS threads. Because of this, OSThreadQueue
is only used for suspended queues.
struct OSThread { int threadId; int priority; void *threadSpecific; struct OSThread *next; } struct OSThreadQueue { struct OSThread *head; struct OSThread *tail; }
Mutexes
Mutexes are implemented as message queues that are read from to lock the mutex and sent to to unlock the mutex.
struct OSMutex { int mqid; int mq; int count; int owner; // thread id }