Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | wait_object: Refactor to allow waking up a single thread. | bunnei | 2018-01-07 | 1 | -15/+22 |
| | |||||
* | Merge pull request #2967 from Subv/thread_wakeup_callbacks | Sebastian Valle | 2017-09-30 | 1 | -7/+4 |
|\ | | | | | Kernel/Threads: When putting a thread to wait, specify a function to execute when it is awoken | ||||
| * | Kernel/Threads: When putting a thread to wait, specify a function to execute when it is awoken. | Subv | 2017-09-28 | 1 | -7/+4 |
| | | | | | | | | | | | | This change makes for a clearer (less confusing) path of execution in the scheduler, now the code to execute when a thread awakes is closer to the code that puts the thread to sleep (WaitSynch1, WaitSynchN). It also allows us to implement the special wake up behavior of ReplyAndReceive without hacking up WaitObject::WakeupAllWaitingThreads. If savestates are desired in the future, we can change this implementation to one similar to the CoreTiming event system, where we first register the callback functions at startup and assign their identifiers to the Thread callback variable instead of directly assigning a lambda to the wake up callback variable. | ||||
* | | Fixed type conversion ambiguity | Huw Pascoe | 2017-09-30 | 1 | -1/+1 |
|/ | |||||
* | Kernel: Move WaitObject to a separate file | Yuri Kunde Schlesner | 2017-05-30 | 1 | -0/+99 |
Now that HandleTable doesn't directly depend on WaitObject anymore, this can be separated from the main kernel.h header. |