Built with Alectryon, running Coq+SerAPI v8.20.0+0.20.0. Bubbles () indicate interactive fragments: hover for details, tap to reveal contents. Use Ctrl+↑Ctrl+↓ to navigate, Ctrl+🖱️ to focus. On Mac, use ⌘ instead of Ctrl.
[Loading ML file ssrmatching_plugin.cmxs (using legacy method) ... done]
[Loading ML file ssreflect_plugin.cmxs (using legacy method) ... done]
[Loading ML file ring_plugin.cmxs (using legacy method) ... done]
Serlib plugin: coq-elpi.elpi is not available: serlib support is missing.
Incremental checking for commands in this plugin will be impacted.
[Loading ML file coq-elpi.elpi ... done]
[Loading ML file zify_plugin.cmxs (using legacy method) ... done]
[Loading ML file micromega_core_plugin.cmxs (using legacy method) ... done]
[Loading ML file micromega_plugin.cmxs (using legacy method) ... done]
[Loading ML file btauto_plugin.cmxs (using legacy method) ... done]
Notation"_ + _" was already used in scope nat_scope.
[notation-overridden,parsing,default]
Notation"_ - _" was already used in scope nat_scope.
[notation-overridden,parsing,default]
Notation"_ <= _" was already used in scope nat_scope.
[notation-overridden,parsing,default]
Notation"_ < _" was already used in scope nat_scope.
[notation-overridden,parsing,default]
Notation"_ >= _" was already used in scope nat_scope.
[notation-overridden,parsing,default]
Notation"_ > _" was already used in scope nat_scope.
[notation-overridden,parsing,default]
Notation"_ <= _ <= _" was already used in scope
nat_scope. [notation-overridden,parsing,default]
Notation"_ < _ <= _" was already used in scope
nat_scope. [notation-overridden,parsing,default]
Notation"_ <= _ < _" was already used in scope
nat_scope. [notation-overridden,parsing,default]
Notation"_ < _ < _" was already used in scope
nat_scope. [notation-overridden,parsing,default]
Notation"_ * _" was already used in scope nat_scope.
[notation-overridden,parsing,default]
Require Export prosa.model.task.preemption.parameters.(** * Task Model with Floating Non-Preemptive Regions *)(** In this file, we instantiate the specific task model of (usually) preemptive tasks with "floating" non-preemptive regions, i.e., with jobs that exhibit non-preemptive segments of bounded length at unpredictable points during their execution. *)(** ** Model Validity *)(** To begin with, we introduce requirements that the function [task_max_nonpr_segment] must satisfy to be coherent with the floating non-preemptive regions model. *)SectionValidModelWithFloatingNonpreemptiveRegions.(** Consider any type of tasks ... *)Context {Task : TaskType}.(** ... with a bound on the maximum non-preemptive segment length ... *)Context `{TaskMaxNonpreemptiveSegment Task}.(** ... and any type of limited-preemptive jobs associated with these tasks ... *)Context {Job : JobType}.Context `{JobTask Job Task}.(** ... with execution costs and specific preemption points. *)Context `{JobCost Job}.Context `{JobPreemptionPoints Job}.(** We assume limited-preemptive jobs. *)#[local] Existing Instancelimited_preemptive_job_model.(** Consider any arrival sequence. *)Variablearr_seq : arrival_sequence Job.(** We require [task_max_nonpreemptive_segment (job_task j)] to be an upper bound of the length of the maximum nonpreemptive segment of job [j]. *)Definitionjob_respects_task_max_np_segment :=
forall (j : Job),
arrives_in arr_seq j ->
job_max_nonpreemptive_segment j <= task_max_nonpreemptive_segment (job_task j).(** A model with floating nonpreemptive regions is valid if it is both valid a the job level and jobs respect the upper bound of their task. *)Definitionvalid_model_with_floating_nonpreemptive_regions :=
valid_limited_preemptions_job_model arr_seq /\
job_respects_task_max_np_segment.EndValidModelWithFloatingNonpreemptiveRegions.(** ** Run-to-Completion Threshold *)(** In this section, we instantiate the task-level run-to-completion threshold for the model with floating non-preemptive regions. *)SectionTaskRTCThresholdFloatingNonPreemptiveRegions.(** Consider any type of tasks with a WCET bound.*)Context {Task : TaskType}.Context `{TaskCost Task}.(** In the model with floating non-preemptive regions, there is no static information about the placement of preemption points in all jobs, i.e., it is impossible to predict when exactly a job will be preemptable. Thus, the only safe run-to-completion threshold is [task cost]. *)#[local] Instancefloating_preemptive_rtc_threshold : TaskRunToCompletionThreshold Task :=
task_cost.EndTaskRTCThresholdFloatingNonPreemptiveRegions.