1a5d6de0d4
Conceptually, it doesn't make sense for a thread to be able to persist the lifetime of a scheduler. A scheduler should be taking care of the threads; the threads should not be taking care of the scheduler. If the threads outlive the scheduler (or we simply don't actually terminate/shutdown the threads), then it should be considered a bug that we need to fix. Attributing this to balika011, as they opened #1317 to attempt to fix this in a similar way, but my refactoring of the kernel code caused quite a few conflicts. |
||
|---|---|---|
| .. | ||
| address_arbiter.cpp | ||
| address_arbiter.h | ||
| client_port.cpp | ||
| client_port.h | ||
| client_session.cpp | ||
| client_session.h | ||
| errors.h | ||
| event.cpp | ||
| event.h | ||
| handle_table.cpp | ||
| handle_table.h | ||
| hle_ipc.cpp | ||
| hle_ipc.h | ||
| kernel.cpp | ||
| kernel.h | ||
| mutex.cpp | ||
| mutex.h | ||
| object.cpp | ||
| object.h | ||
| process.cpp | ||
| process.h | ||
| resource_limit.cpp | ||
| resource_limit.h | ||
| scheduler.cpp | ||
| scheduler.h | ||
| server_port.cpp | ||
| server_port.h | ||
| server_session.cpp | ||
| server_session.h | ||
| session.cpp | ||
| session.h | ||
| shared_memory.cpp | ||
| shared_memory.h | ||
| svc_wrap.h | ||
| svc.cpp | ||
| svc.h | ||
| thread.cpp | ||
| thread.h | ||
| timer.cpp | ||
| timer.h | ||
| vm_manager.cpp | ||
| vm_manager.h | ||
| wait_object.cpp | ||
| wait_object.h | ||