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]
(** * Preemption Model Compliance *) (** A preemption model restricts when jobs can be preempted. In this module, we specify the corresponding semantics, i.e., how a valid schedule must be restricted to be compliant with a given preemption model. *) Section ScheduleWithLimitedPreemptions. (** Consider any type of jobs, ... *) Context {Job : JobType}. (** ... any processor model, ... *) Context {PState : ProcessorState Job}. (** ... and any preemption model. *) Context `{JobPreemptable Job}. (** Consider any arrival sequence ... *) Variable arr_seq : arrival_sequence Job. (** ... and a schedule of the jobs in the arrival sequence. *) Variable sched : schedule PState. (** We say that a schedule respects the preemption model given by [job_preemptable] if non-preemptable jobs remain scheduled. *) Definition schedule_respects_preemption_model := forall j t, arrives_in arr_seq j -> ~~ job_preemptable j (service sched j t) -> scheduled_at sched j t. End ScheduleWithLimitedPreemptions.