Andreas Kling 2c74533ba6 Kernel: Don't register thread as custom data for WaitQueueBlocker ...

When adding a WaitQueueBlocker to a WaitQueue, it stored the blocked
thread in the registration's custom "void* data" slot.
This was only used to print the Thread* in some debug logging.

Now that Blocker always knows its origin Thread, we can simply add
a Blocker::thread() accessor and then get the blocked Thread& from
there. No need to register custom data.

2021-08-24 01:57:11 +02:00

3.2 KiB

Raw Blame History

View Raw