mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2024-09-20 01:37:39 +03:00
2c74533ba6
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.
41 lines
907 B
C++
41 lines
907 B
C++
/*
|
|
* Copyright (c) 2020, the SerenityOS developers.
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <AK/Atomic.h>
|
|
#include <Kernel/Locking/Spinlock.h>
|
|
#include <Kernel/Thread.h>
|
|
|
|
namespace Kernel {
|
|
|
|
class WaitQueue final : public Thread::BlockerSet {
|
|
public:
|
|
u32 wake_one();
|
|
u32 wake_n(u32 wake_count);
|
|
u32 wake_all();
|
|
|
|
template<class... Args>
|
|
Thread::BlockResult wait_on(const Thread::BlockTimeout& timeout, Args&&... args)
|
|
{
|
|
return Thread::current()->block<Thread::WaitQueueBlocker>(timeout, *this, forward<Args>(args)...);
|
|
}
|
|
|
|
template<class... Args>
|
|
void wait_forever(Args&&... args)
|
|
{
|
|
(void)Thread::current()->block<Thread::WaitQueueBlocker>({}, *this, forward<Args>(args)...);
|
|
}
|
|
|
|
protected:
|
|
virtual bool should_add_blocker(Thread::Blocker& b, void*) override;
|
|
|
|
private:
|
|
bool m_wake_requested { false };
|
|
};
|
|
|
|
}
|