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 Import prosa.util.nat.(** * Job Model Parameter for Jobs Exhibiting Release Jitter *)(** If a job exhibits release jitter, it is not immediately available for execution upon arrival, and can be scheduled only after its release, which occurs some (bounded) time after its arrival. We model this with the [job_jitter] parameter, which maps each job to its jitter duration. *)ClassJobJitter (Job : JobType) := job_jitter : Job -> duration.(** * Readiness of Jobs with Release Jitter *)(** Based on the job model's jitter parameter, we define the readiness predicate for jogs with release jitter (and no self-suspensions). *)SectionReadinessOfJitteryJobs.(** Consider any kind of jobs... *)Context {Job : JobType}.(** ... and any kind of processor state. *)Context {PState : ProcessorState Job}.(** Suppose jobs have an arrival time, a cost, and exhibit release jitter. *)Context `{JobArrival Job} `{JobCost Job} `{JobJitter Job}.(** We say that a job is released at a time [t] after its arrival if the job's release jitter has passed. *)Definitionis_released (j : Job) (t : instant) := job_arrival j + job_jitter j <= t.(** Based on the predicate [is_released], it is easy to state the notion of readiness for jobs subject to release jitter: a job is ready only if it is released and not yet complete. *)#[local,program] Instancejitter_ready_instance : JobReady Job PState :=
{
job_ready sched j t := is_released j t && ~~ completed_by sched j t
}.