mirror of
https://github.com/RGBCube/serenity
synced 2025-07-25 21:27:35 +00:00
Kernel: Update terminology around Thread's "blocking mutex"
It's more accurate to say that we're blocking on a mutex, rather than blocking on a lock. The previous terminology made sense when this code was using something called Kernel::Lock, but since it was renamed to Kernel::Mutex, this updates brings the language back in sync.
This commit is contained in:
parent
dca5fe69eb
commit
b0e5406ae2
3 changed files with 19 additions and 19 deletions
|
@ -870,7 +870,7 @@ public:
|
|||
return block_impl(timeout, blocker);
|
||||
}
|
||||
|
||||
u32 unblock_from_lock(Kernel::Mutex&);
|
||||
u32 unblock_from_mutex(Kernel::Mutex&);
|
||||
void unblock_from_blocker(Blocker&);
|
||||
void unblock(u8 signal = 0);
|
||||
|
||||
|
@ -1227,7 +1227,7 @@ private:
|
|||
Optional<Memory::VirtualRange> m_thread_specific_range;
|
||||
Array<SignalActionData, NSIG> m_signal_action_data;
|
||||
Blocker* m_blocker { nullptr };
|
||||
Kernel::Mutex* m_blocking_lock { nullptr };
|
||||
Kernel::Mutex* m_blocking_mutex { nullptr };
|
||||
u32 m_lock_requested_count { 0 };
|
||||
IntrusiveListNode<Thread> m_blocked_threads_list_node;
|
||||
LockRank m_lock_rank_mask { LockRank::None };
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue