Built with Alectryon, running Coq+SerAPI v8.15.0+0.15.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.
Notation "[ rel _ _ | _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
Notation "[ rel _ _ : _ | _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
Notation "[ rel _ _ in _ & _ | _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
Notation "[ rel _ _ in _ & _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
Notation "[ rel _ _ in _ | _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
Notation "[ rel _ _ in _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
Notation "_ + _" was already used in scope nat_scope. [notation-overridden,parsing]
Notation "_ - _" was already used in scope nat_scope. [notation-overridden,parsing]
Notation "_ <= _" was already used in scope nat_scope. [notation-overridden,parsing]
Notation "_ < _" was already used in scope nat_scope. [notation-overridden,parsing]
Notation "_ >= _" was already used in scope nat_scope. [notation-overridden,parsing]
Notation "_ > _" was already used in scope nat_scope. [notation-overridden,parsing]
Notation "_ <= _ <= _" was already used in scope nat_scope. [notation-overridden,parsing]
Notation "_ < _ <= _" was already used in scope nat_scope. [notation-overridden,parsing]
Notation "_ <= _ < _" was already used in scope nat_scope. [notation-overridden,parsing]
Notation "_ < _ < _" was already used in scope nat_scope. [notation-overridden,parsing]
Notation "_ * _" was already used in scope nat_scope. [notation-overridden,parsing]
Notation "[ rel _ _ | _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
Notation "[ rel _ _ : _ | _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
Notation "[ rel _ _ in _ & _ | _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
Notation "[ rel _ _ in _ & _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
Notation "[ rel _ _ in _ | _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
Notation "[ rel _ _ in _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
Notation "[ rel _ _ | _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
Notation "[ rel _ _ : _ | _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
Notation "[ rel _ _ in _ & _ | _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
Notation "[ rel _ _ in _ & _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
Notation "[ rel _ _ in _ | _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
Notation "[ rel _ _ in _ ]" was already used in scope fun_scope. [notation-overridden,parsing]
(** * Priority-Driven Schedules *) (** We now define what it means for a schedule to respect a priority in the presence of jobs with non-preemptive segments. We only specify a definition for JLDP policies since JLFP and FP policies can be used with this definition through the canonical conversions (see model.priority.classes). NB: For legacy reasons, the below definition is currently specific to ideal uniprocessor schedules. Removal of this limitation is future work. *) Section Priority. (** Consider any type of tasks ... *) Context {Task : TaskType}. (** ... and any type of jobs associated with these tasks. *) Context {Job : JobType}. Context `{JobTask Job Task}. (** Suppose jobs have an arrival time, a cost, ... *) Context `{JobArrival Job}. Context `{JobCost Job}. (** ... and consider any preemption model and notion of readiness. *) Context `{JobPreemptable Job}. Context {jr : JobReady Job (ideal.processor_state Job)}. (** Given any job arrival sequence... *) Variable arr_seq : arrival_sequence Job. (** ...and an ideal uniprocessor schedule of these jobs, *) Variable sched : schedule (ideal.processor_state Job). (** we say that a priority policy is respected by the schedule iff, at every preemption point, the priority of the scheduled job is higher than or equal to the priority of any backlogged job. We define three separate notions of priority policy compliance based on the three types of scheduling policies : [JLDP]... *) Definition respects_JLDP_policy_at_preemption_point (policy: JLDP_policy Job) := forall j j_hp t, arrives_in arr_seq j -> preemption_time sched t -> backlogged sched j t -> scheduled_at sched j_hp t -> hep_job_at t j_hp j. (** ... [JLFP], and... *) Definition respects_JLFP_policy_at_preemption_point (policy: JLFP_policy Job) := respects_JLDP_policy_at_preemption_point policy. (** [FP]. *) Definition respects_FP_policy_at_preemption_point (policy: FP_policy Task) := respects_JLDP_policy_at_preemption_point (FP_to_JLFP Job Task ). End Priority.