Citron

Author	SHA1	Message	Date
Lioncash	5eb057f422	kernel/object: Amend handle types to distinguish between readable and writable events Two kernel object should absolutely never have the same handle ID type. This can cause incorrect behavior when it comes to retrieving object types from the handle table. In this case it allows converting a WritableEvent into a ReadableEvent and vice-versa, which is undefined behavior, since the object types are not the same. This also corrects ClearEvent() to check both kernel types like the kernel itself does.	2018-12-04 02:20:47 -05:00
Zach Hilman	170d707850	hle_ipc: Refactor SleepClientThread to avoid ReadableEvent	2018-11-29 09:14:20 -05:00
Zach Hilman	a342bcc9b1	kernel/event: Reference ReadableEvent from WritableEvent	2018-11-29 08:48:40 -05:00
Zach Hilman	c713383816	kernel: Divide Event into ReadableEvent and WritableEvent More hardware accurate. On the actual system, there is a differentiation between the signaler and signalee, they form a client/server relationship much like ServerPort and ClientPort.	2018-11-29 08:42:26 -05:00