+/** Implementation note on the mallocators:
+ *
+ * Mallocators and memory mess introduced by model-checking do not mix well
+ * together: the mallocator will give standard memory when we are using raw
+ * memory (so these blocks are killed on restore) and the contrary (so these
+ * blocks will leak across restores).
+ *
+ * In addition, model-checking is activated when the command-line arguments
+ * are parsed, at the beginning of main, while most of the mallocators are
+ * created during the constructor functions launched from xbt_preinit, before
+ * the beginning of the main function.
+ *
+ * We want the code as fast as possible when they are active while we can deal
+ * with a little slow-down when they are inactive. So we start the mallocators
+ * as inactive. When they are so, they check at each use whether they should
+ * switch to the fast active mode or should stay in inactive mode.
+ * Finally, we give external elements a way to switch them
+ * all to the active mode (through xbt_mallocator_initialization_is_done).
+ *
+ * This design avoids to store all mallocators somewhere for later conversion,
+ * which would be hard to achieve provided that all our data structures use
+ * some mallocators internally...
+ */
+
+/* Value != 0 when the framework configuration is done. Value > 1 if the
+ * mallocators should be protected from concurrent accesses. */
+static int initialization_done = 0;
+
+static XBT_INLINE void lock_reset(xbt_mallocator_t m)
+{
+ m->lock = 0;
+}
+
+static XBT_INLINE void lock_acquire(xbt_mallocator_t m)
+{
+ if (initialization_done > 1) {
+ int *lock = &m->lock;
+ while (__sync_lock_test_and_set(lock, 1))
+ /* nop */;
+ }
+}
+
+static XBT_INLINE void lock_release(xbt_mallocator_t m)
+{
+ if (initialization_done > 1)
+ __sync_lock_release(&m->lock);
+}
+
+/**
+ * This function must be called once the framework configuration is done. If not,
+ * mallocators will never get used. Check the implementation notes in
+ * src/xbt/mallocator.c for the justification of this.
+ *
+ * For example, surf_config uses this function to tell to the mallocators that
+ * the simgrid
+ * configuration is now finished and that it can create them if not done yet */
+void xbt_mallocator_initialization_is_done(int protect)
+{
+ initialization_done = protect ? 2 : 1;
+}
+
+/** used by the module to know if it's time to activate the mallocators yet */
+static XBT_INLINE int xbt_mallocator_is_active(void) {
+#if MALLOCATOR_COMPILED_IN
+ return initialization_done && !MC_is_active();
+#else
+ return 0;
+#endif
+}
+