You can specify a start time and a kill time in the deployment
file. See all *_d.xml files in this directory.
+ - <b>Using Pstates on a host</b>
+ @ref examples/msg/energy-pstate/energy-pstate.c\n
+ Show how define a set of pstates for a host and how the current
+ pstate can be accessed/changed with @ref MSG_get_host_current_power_peak and @ref MSG_set_host_pstate.
+ See also the platform XML file for have a details on how to declare the CPU capacity for each pstate.
+
@section msg_ex_tracing Tracing and visualization features
Tracing can be activated by various configuration options which
displayed as arrows in a Gantt-chart visualization. Recommanded
options to that extend:
@verbatim -cfg=tracing:yes --cfg=tracing/msg/process:yes
- @endverbatim
-
+ @endverbatim
+
TODO: These tracing examples should be integrated in the examples to
not duplicate the C files. A full command line to see the result in
the right tool (viva/vite/FrameSoc) should be given along with some
@ref examples/s4u/actor-migration/s4u-actor-migration.cpp \n
Actors can move or be moved from a host to another with the @ref migrate method.
+ - <b>Using Pstates on a host</b>
+ @ref examples/s4u/energy-pstate/s4u-energy-pstate.c\n
+ Show how define a set of pstates for a host and how the current
+ pstate can be accessed/changed with @ref getPstateSpeed and @ref sg_host_set_pstate.
+ See also the platform XML file for have a details on how to declare the CPU capacity for each pstate.
+
@section s4u_ex_synchro Inter-Actor Synchronization
- <b>Mutex: </b> @ref examples/s4u/mutex/s4u-mutex.cpp \n