# Library prosa.analysis.facts.priority.elf

Require Export prosa.model.priority.elf.
Require Export prosa.model.aggregate.workload.
Require Export prosa.analysis.facts.priority.classes.
Require Export prosa.model.schedule.priority_driven.
Require Export prosa.analysis.facts.model.sequential.
Require Export prosa.analysis.facts.priority.sequential.
Require Export prosa.analysis.facts.priority.gel.
In this section, we state and prove some basic facts about the ELF scheduling policy.
Section ELFBasicFacts.
Consider any type of tasks with relative priority points...
Context {Task : TaskType} `{PriorityPoint Task}.
...and jobs of these tasks.
Context {Job : JobType} `{JobTask Job Task} `{JobCost Job} {AR : JobArrival Job}.
Consider any arbitrary FP policy ...
Variable FP : FP_policy Task.
... that is reflexive, transitive, and total.
Hypothesis H_reflexive_priorities : reflexive_task_priorities FP.
Hypothesis H_transitive_priorities : transitive_task_priorities FP.
Hypothesis H_total_priorities : total_task_priorities FP.

## Basic properties of the ELF policy

We first note that, by definition, ELF reduces to GEL for equal-priority tasks.
Remark hep_job_elf_gel :
∀ j j',
ep_task (job_task j) (job_task j') →
(@hep_job _ (ELF FP) j j') = (@hep_job _ (GEL Job Task) j j').
We then show that if we are looking at two jobs of the same task, then hep_job is a statement about their respective arrival times.
Fact hep_job_arrival_elf :
∀ j j',
same_task j j' →
hep_job j j' = (job_arrival j ≤ job_arrival j').
ELF is reflexive.
Lemma ELF_is_reflexive : reflexive_job_priorities (ELF FP).
ELF is transitive.
Lemma ELF_is_transitive : transitive_job_priorities (ELF FP).
ELF is total.
Lemma ELF_is_total : total_job_priorities (ELF FP).
The ELF policy is JLFP_FP_compatible.
Lemma ELF_is_JLFP_FP_compatible :
JLFP_FP_compatible (ELF FP) FP.

## Sequentiality under ELF

The ELF policy satisfies the sequential-tasks hypothesis.
Lemma ELF_respects_sequential_tasks :
policy_respects_sequential_tasks (ELF FP).
In this section, we prove that tasks always execute sequentially in a uniprocessor schedule following the ELF policy.
Section ELFImpliesSequentialTasks.
Consider any valid arrival sequence.
Variable arr_seq : arrival_sequence Job.
Hypothesis H_valid_arrivals : valid_arrival_sequence arr_seq.
Allow for any uniprocessor model.
Context {PState : ProcessorState Job}.
Hypothesis H_uniproc : uniprocessor_model PState.
Next, consider any schedule of the arrival sequence, ...
Variable sched : schedule PState.
... allow for any work-bearing notion of job readiness, ...
Context `{@JobReady Job PState _ AR}.
Hypothesis H_job_ready : work_bearing_readiness arr_seq sched.
... and assume that the schedule is valid.
Hypothesis H_sched_valid : valid_schedule sched arr_seq.
Consider any valid preemption model.
Context `{JobPreemptable Job}.
Hypothesis H_valid_preemption_model : valid_preemption_model arr_seq sched.
Assume an ELF schedule.
Hypothesis H_respects_policy :
respects_JLFP_policy_at_preemption_point arr_seq sched (ELF FP).
To prove sequentiality, we use the lemma early_hep_job_is_scheduled. Clearly, under the ELF priority policy, jobs satisfy the conditions described by the lemma (i.e., given two jobs j1 and j2 from the same task, if j1 arrives earlier than j2, then j1 always has a higher priority than job j2, and hence completes before j2); therefore, ELF implies the sequential_tasks property.
Lemma ELF_implies_sequential_tasks :
sequential_tasks arr_seq sched.
End ELFImpliesSequentialTasks.
End ELFBasicFacts.
We add the above facts into a "Hint Database" basic_rt_facts, so Coq will be able to apply them automatically where needed.
Global Hint Resolve
ELF_is_reflexive
ELF_is_transitive
ELF_is_total
ELF_is_JLFP_FP_compatible
ELF_respects_sequential_tasks
ELF_implies_sequential_tasks
: basic_rt_facts.