X-Git-Url: http://bilbo.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/21f6e059a47df7875f1dacf26ca1eb854f4e887b..40ee10e13b61bfb28374d96ade010a262b5abd44:/include/simgrid/simix.hpp diff --git a/include/simgrid/simix.hpp b/include/simgrid/simix.hpp index 76e1f8fb85..338c3372ae 100644 --- a/include/simgrid/simix.hpp +++ b/include/simgrid/simix.hpp @@ -1,5 +1,4 @@ -/* Copyright (c) 2007-2022. The SimGrid Team. - * All rights reserved. */ +/* Copyright (c) 2007-2023. The SimGrid Team. All rights reserved. */ /* This program is free software; you can redistribute it and/or modify it * under the terms of the license (GNU LGPL) which comes with this package. */ @@ -8,7 +7,6 @@ #define SIMGRID_SIMIX_HPP #include -#include #include #include @@ -19,15 +17,15 @@ XBT_PUBLIC void simcall_run_answered(std::function const& code, simgrid::kernel::actor::SimcallObserver* observer); XBT_PUBLIC void simcall_run_blocking(std::function const& code, simgrid::kernel::actor::SimcallObserver* observer); +XBT_PUBLIC void simcall_run_object_access(std::function const& code, + simgrid::kernel::actor::ObjectAccessSimcallItem* item); -namespace simgrid { -namespace kernel { -namespace actor { +namespace simgrid::kernel::actor { /** Execute some code in kernel context on behalf of the user code. * * Every modification of the environment must be protected this way: every setter, constructor and similar. - * Getters don't have to be protected this way. + * Getters don't have to be protected this way, and setters may use the simcall_object_access() variant (see below). * * This allows deterministic parallel simulation without any locking, even if almost nobody uses parallel simulation in * SimGrid. More interestingly it makes every modification of the simulated world observable by the model-checker, @@ -59,9 +57,32 @@ template typename std::result_of_t simcall_answered(F&& code, Sim return result.get(); } +/** Use a setter on the `item` object. That's a simcall only if running in parallel or with MC activated. + * + * Simulation without MC and without parallelism (contexts/nthreads=1) will not pay the price of a simcall for an + * harmless setter. When running in parallel, you want your write access to be done in a mutual exclusion way, while the + * getters can still occur out of order. + * + * When running in MC, you want to make this access visible to the checker. Actually in this case, it's not visible from + * the checker (and thus still use a fast track) if the setter is called from the actor that created the object. + */ +template typename std::result_of_t simcall_object_access(ObjectAccessSimcallItem* item, F&& code) +{ + // If we are in the maestro, we take the fast path and execute the code directly + if (simgrid::s4u::Actor::is_maestro()) + return std::forward(code)(); + + // If called from another thread, do a real simcall. It will be short-cut on need + using R = typename std::result_of_t; + simgrid::xbt::Result result; + simcall_run_object_access([&result, &code] { simgrid::xbt::fulfill_promise(result, std::forward(code)); }, item); + + return result.get(); +} + /** Execute some code (that does not return immediately) in kernel context * - * This is very similar to simcall() right above, but the calling actor will not get rescheduled until + * This is very similar to simcall_answered() above, but the calling actor will not get rescheduled until * actor->simcall_answer() is called explicitly. * * This is meant for blocking actions. For example, locking a mutex is a blocking simcall. @@ -92,14 +113,5 @@ auto simcall_blocking(F&& code, Observer* observer) -> decltype(observer->get_re simcall_blocking(std::forward(code), static_cast(observer)); return observer->get_result(); } -} // namespace actor -} // namespace kernel - -namespace simix { - -XBT_PUBLIC void unblock(smx_actor_t process); - -} // namespace simix -} // namespace simgrid - +} // namespace simgrid::kernel::actor #endif