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.analysis.definitions.sbf.pred.(** * Plain Supply Bound Functions (SBFs) *)(** ** Parameter Semantics *)(** In the following, we define the semantics of the classical supply bound functions (SBF). *)SectionSupplyBoundFunctions.(** Consider any type of jobs, ... *)Context {Job : JobType}.(** ... any kind of processor state model, ... *)Context `{PState : ProcessorState Job}.(** ... any valid arrival sequence, and ... *)Variablearr_seq : arrival_sequence Job.(** ... any schedule. *)Variablesched : schedule PState.(** We say that the SBF is respected if, for any time interval <<[t1, t2)>>, at least [SBF (t2 - t1)] cumulative supply is provided within the given interval. In other words, the SBF lower-bounds the provided supply. *)Definitionsupply_bound_function_respected (SBF : duration -> work) :=
pred_sbf_respected arr_seq sched (fun___ => True) SBF.(** We say that a plain SBF is valid iff it is valid w.r.t. a predicate that is always true (i.e., [fun _ _ _ => True]). *)Definitionvalid_supply_bound_function (SBF : duration -> work) :=
valid_pred_sbf arr_seq sched (fun___ => True) SBF.(** Suppose we are given an SBF characterizing the schedule. *)Context {SBF : SupplyBoundFunction}.(** Note that the predicate [(fun _ _ _ => True)] can be easily discarded. *)