2014-02-10 09:10:30 +08:00
|
|
|
/**************************************************************************/
|
|
|
|
/* semaphore.h */
|
|
|
|
/**************************************************************************/
|
|
|
|
/* This file is part of: */
|
|
|
|
/* GODOT ENGINE */
|
|
|
|
/* https://godotengine.org */
|
|
|
|
/**************************************************************************/
|
|
|
|
/* Copyright (c) 2014-present Godot Engine contributors (see AUTHORS.md). */
|
|
|
|
/* Copyright (c) 2007-2014 Juan Linietsky, Ariel Manzur. */
|
|
|
|
/* */
|
|
|
|
/* Permission is hereby granted, free of charge, to any person obtaining */
|
|
|
|
/* a copy of this software and associated documentation files (the */
|
|
|
|
/* "Software"), to deal in the Software without restriction, including */
|
|
|
|
/* without limitation the rights to use, copy, modify, merge, publish, */
|
|
|
|
/* distribute, sublicense, and/or sell copies of the Software, and to */
|
|
|
|
/* permit persons to whom the Software is furnished to do so, subject to */
|
|
|
|
/* the following conditions: */
|
|
|
|
/* */
|
|
|
|
/* The above copyright notice and this permission notice shall be */
|
|
|
|
/* included in all copies or substantial portions of the Software. */
|
|
|
|
/* */
|
|
|
|
/* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, */
|
|
|
|
/* EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF */
|
|
|
|
/* MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. */
|
|
|
|
/* IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY */
|
|
|
|
/* CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, */
|
|
|
|
/* TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE */
|
|
|
|
/* SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. */
|
|
|
|
/**************************************************************************/
|
2018-01-05 07:50:27 +08:00
|
|
|
|
2014-02-10 09:10:30 +08:00
|
|
|
#ifndef SEMAPHORE_H
|
|
|
|
#define SEMAPHORE_H
|
|
|
|
|
2020-11-08 06:33:38 +08:00
|
|
|
#include "core/error/error_list.h"
|
2019-07-29 23:59:18 +08:00
|
|
|
#include "core/typedefs.h"
|
2023-01-28 20:34:06 +08:00
|
|
|
#ifdef DEBUG_ENABLED
|
|
|
|
#include "core/error/error_macros.h"
|
|
|
|
#endif
|
2019-07-29 23:59:18 +08:00
|
|
|
|
2023-11-18 03:44:38 +08:00
|
|
|
#ifdef MINGW_ENABLED
|
|
|
|
#define MINGW_STDTHREAD_REDUNDANCY_WARNING
|
|
|
|
#include "thirdparty/mingw-std-threads/mingw.condition_variable.h"
|
|
|
|
#include "thirdparty/mingw-std-threads/mingw.mutex.h"
|
|
|
|
#define THREADING_NAMESPACE mingw_stdthread
|
|
|
|
#else
|
2019-07-29 23:59:18 +08:00
|
|
|
#include <condition_variable>
|
|
|
|
#include <mutex>
|
2023-11-18 03:44:38 +08:00
|
|
|
#define THREADING_NAMESPACE std
|
|
|
|
#endif
|
2014-02-10 09:10:30 +08:00
|
|
|
|
|
|
|
class Semaphore {
|
2019-07-29 23:59:18 +08:00
|
|
|
private:
|
2023-11-18 03:44:38 +08:00
|
|
|
mutable THREADING_NAMESPACE::mutex mutex;
|
|
|
|
mutable THREADING_NAMESPACE::condition_variable condition;
|
2023-01-27 19:36:01 +08:00
|
|
|
mutable uint32_t count = 0; // Initialized as locked.
|
2023-01-28 20:34:06 +08:00
|
|
|
#ifdef DEBUG_ENABLED
|
|
|
|
mutable uint32_t awaiters = 0;
|
|
|
|
#endif
|
2019-07-29 23:59:18 +08:00
|
|
|
|
|
|
|
public:
|
WorkerThreadPool: Overhaul scheduling and synchronization
This commits rewrites the sync logic in a way that the
`use_system_threads_for_low_priority_tasks` setting, which was added due to
the lack of a cross-platform wait-for-multiple-objects functionality, can be
removed (it's as if it was effectively hardcoded to `false`).
With the new implementation, we have the best of both worlds: threads don't
have to poll, plus no bespoke threads are used.
In addition, regarding deadlock prevention, since not every possible case of
wait-deadlock could be avoided, this commits removes the current best-effort
avoidance mechanisms and keeps only a simple, pessimistic way of detection.
It turns out that the only current user of deadlock prevention, ResourceLoader,
works fine with it and so every possible situation in resource loading is now
properly handled, with no possibilities of deadlocking. There's a comment in
the code with further details.
Lastly, a potential for load tasks never being awaited/disposed is cleared.
2024-01-06 00:39:26 +08:00
|
|
|
_ALWAYS_INLINE_ void post(uint32_t p_count = 1) const {
|
2023-01-27 19:36:01 +08:00
|
|
|
std::lock_guard lock(mutex);
|
WorkerThreadPool: Overhaul scheduling and synchronization
This commits rewrites the sync logic in a way that the
`use_system_threads_for_low_priority_tasks` setting, which was added due to
the lack of a cross-platform wait-for-multiple-objects functionality, can be
removed (it's as if it was effectively hardcoded to `false`).
With the new implementation, we have the best of both worlds: threads don't
have to poll, plus no bespoke threads are used.
In addition, regarding deadlock prevention, since not every possible case of
wait-deadlock could be avoided, this commits removes the current best-effort
avoidance mechanisms and keeps only a simple, pessimistic way of detection.
It turns out that the only current user of deadlock prevention, ResourceLoader,
works fine with it and so every possible situation in resource loading is now
properly handled, with no possibilities of deadlocking. There's a comment in
the code with further details.
Lastly, a potential for load tasks never being awaited/disposed is cleared.
2024-01-06 00:39:26 +08:00
|
|
|
count += p_count;
|
|
|
|
for (uint32_t i = 0; i < p_count; ++i) {
|
|
|
|
condition.notify_one();
|
|
|
|
}
|
2019-07-29 23:59:18 +08:00
|
|
|
}
|
|
|
|
|
2020-03-03 16:26:42 +08:00
|
|
|
_ALWAYS_INLINE_ void wait() const {
|
2023-11-18 03:44:38 +08:00
|
|
|
THREADING_NAMESPACE::unique_lock lock(mutex);
|
2023-01-28 20:34:06 +08:00
|
|
|
#ifdef DEBUG_ENABLED
|
|
|
|
++awaiters;
|
|
|
|
#endif
|
2023-01-27 19:36:01 +08:00
|
|
|
while (!count) { // Handle spurious wake-ups.
|
|
|
|
condition.wait(lock);
|
2020-05-14 22:41:43 +08:00
|
|
|
}
|
2023-01-28 20:34:06 +08:00
|
|
|
--count;
|
|
|
|
#ifdef DEBUG_ENABLED
|
|
|
|
--awaiters;
|
|
|
|
#endif
|
2019-07-29 23:59:18 +08:00
|
|
|
}
|
|
|
|
|
2020-03-03 16:26:42 +08:00
|
|
|
_ALWAYS_INLINE_ bool try_wait() const {
|
2023-01-27 19:36:01 +08:00
|
|
|
std::lock_guard lock(mutex);
|
|
|
|
if (count) {
|
|
|
|
count--;
|
2019-07-29 23:59:18 +08:00
|
|
|
return true;
|
2023-01-27 19:36:01 +08:00
|
|
|
} else {
|
|
|
|
return false;
|
2019-07-29 23:59:18 +08:00
|
|
|
}
|
|
|
|
}
|
2023-01-28 20:34:06 +08:00
|
|
|
|
|
|
|
#ifdef DEBUG_ENABLED
|
|
|
|
~Semaphore() {
|
|
|
|
// Destroying an std::condition_variable when not all threads waiting on it have been notified
|
|
|
|
// invokes undefined behavior (e.g., it may be nicely destroyed or it may be awaited forever.)
|
|
|
|
// That means other threads could still be running the body of std::condition_variable::wait()
|
|
|
|
// but already past the safety checkpoint. That's the case for instance if that function is already
|
|
|
|
// waiting to lock again.
|
|
|
|
//
|
|
|
|
// We will make the rule a bit more restrictive and simpler to understand at the same time: there
|
|
|
|
// should not be any threads at any stage of the waiting by the time the semaphore is destroyed.
|
|
|
|
//
|
|
|
|
// We do so because of the following reasons:
|
|
|
|
// - We have the guideline that threads must be awaited (i.e., completed), so the waiting thread
|
|
|
|
// must be completely done by the time the thread controlling it finally destroys the semaphore.
|
|
|
|
// Therefore, only a coding mistake could make the program run into such a attempt at premature
|
|
|
|
// destruction of the semaphore.
|
|
|
|
// - In scripting, given that Semaphores are wrapped by RefCounted classes, in general it can't
|
|
|
|
// happen that a thread is trying to destroy a Semaphore while another is still doing whatever with
|
|
|
|
// it, so the simplification is mostly transparent to script writers.
|
|
|
|
// - The redefined rule can be checked for failure to meet it, which is what this implementation does.
|
|
|
|
// This is useful to detect a few cases of potential misuse; namely:
|
|
|
|
// a) In scripting:
|
|
|
|
// * The coder is naughtily dealing with the reference count causing a semaphore to die prematurely.
|
|
|
|
// * The coder is letting the project reach its termination without having cleanly finished threads
|
|
|
|
// that await on semaphores (or at least, let the usual semaphore-controlled loop exit).
|
|
|
|
// b) In the native side, where Semaphore is not a ref-counted beast and certain coding mistakes can
|
|
|
|
// lead to its premature destruction as well.
|
|
|
|
//
|
|
|
|
// Let's let users know they are doing it wrong, but apply a, somewhat hacky, countermeasure against UB
|
|
|
|
// in debug builds.
|
|
|
|
std::lock_guard lock(mutex);
|
|
|
|
if (awaiters) {
|
|
|
|
WARN_PRINT(
|
|
|
|
"A Semaphore object is being destroyed while one or more threads are still waiting on it.\n"
|
|
|
|
"Please call post() on it as necessary to prevent such a situation and so ensure correct cleanup.");
|
|
|
|
// And now, the hacky countermeasure (i.e., leak the condition variable).
|
2023-11-18 03:44:38 +08:00
|
|
|
new (&condition) THREADING_NAMESPACE::condition_variable();
|
2023-01-28 20:34:06 +08:00
|
|
|
}
|
|
|
|
}
|
|
|
|
#endif
|
2019-07-29 23:59:18 +08:00
|
|
|
};
|
|
|
|
|
2020-03-25 18:10:34 +08:00
|
|
|
#endif // SEMAPHORE_H
|