add to the doc:

* the SC_HYPERVISOR_SAMPLE_CRITERIA
* the new fields of the sched_ctx_wrapper

doc/doxygen/chapters/api/scheduling_context_hypervisor.doxy

@@ -102,6 +102,8 @@ the performance counters.
 	The number of flops submitted to this ctx
 \var sc_hypervisor_wrapper::remaining_flops
         The number of flops that still have to be executed by the workers in the context
+\var sc_hypervisor_wrapper::ready_flops
+	The number of flops corresponding to the ready tasks in this context
 \var sc_hypervisor_wrapper::start_time
         The time when he started executed
 \var sc_hypervisor_wrapper::real_start_time
@@ -111,7 +113,12 @@ the performance counters.
 \var sc_hypervisor_wrapper::mutex
 	The mutex needed to synchronize the acknowledgment of the workers into 
 	the receiver context
-	
+\var sc_hypervisor_wrapper::total_flops_available
+	A boolean indicating if the hypervisor can use the flops corresponding to 
+	the entire execution of the context
+\var sc_hypervisor_wrapper::nready_tasks
+	The number of ready tasks in a context
+
 \struct sc_hypervisor_resize_ack
 \ingroup API_Scheduling_Context_Hypervisor
 This structures checks if the workers moved to another context

doc/doxygen/chapters/environment_variables.doxy

@@ -610,4 +610,14 @@ before removing them from the previous one. Once this workers are clearly taken
 into the new context (a task was poped there) we remove them from the previous one. However if the application
 would like that the change in the distribution of workers should change right away this variable should be set to 0
 </dl>
+
+<dt>SC_HYPERVISOR_SAMPLE_CRITERIA</dt>
+<dd>
+\anchor SC_HYPERVISOR_SAMPLE_CRITERIA
+\addindex __env__SC_HYPERVISOR_SAMPLE_CRITERIA
+By default the hypervisor uses a sample of flops when computing the speed of the contexts and of the workers.
+If this variable is set to <c>time</c> the hypervisor uses a sample of time (10% of an aproximation of the total
+execution time of the application)
+</dl>
+
 */