Library prosa.results.fixed_priority.rta.comp.fully_preemptive

RTA for Fully Preemptive FP Scheduling with Computed Fixpoints

This module refines the general response-time bound for fully preemptive fixed-priority scheduling in prosa.results.fixed_priority.rta.fully_preemptive. Whereas the general result assumes that all fixpoints are given, i.e., that they have been found somehow without imposing any assumptions on how they have been found, here we compute all relevant fixpoints using the procedures provided in prosa.util.fixpoint.

Problem Setup and Analysis Context

To begin, we must set up the context as in prosa.results.fixed_priority.rta.fully_preemptive.
We assume ideal uni-processor schedules.
  #[local] Existing Instance ideal.processor_state.

Consider any type of tasks characterized by WCETs ...
  Context {Task : TaskType} `{TaskCost Task}.

... and any type of jobs associated with these tasks, where each job is characterized by an arrival time and an execution cost.
  Context {Job : JobType} `{JobTask Job Task} `{JobArrival Job} `{JobCost Job}.

We assume that jobs and tasks are fully preemptive.
   #[local] Existing Instance fully_preemptive_job_model.
   #[local] Existing Instance fully_preemptive_task_model.
   #[local] Existing Instance fully_preemptive_rtc_threshold.

Consider any arrival sequence with consistent, non-duplicate arrivals.
Consider an arbitrary task set ts, ...
  Variable ts : list Task.

... assume that all jobs come from the task set, ...
... and that the cost of a job does not exceed the task's WCET .
Let max_arrivals be a family of valid arrival curves, i.e., for any task tsk in ts, max_arrival tsk is (1) an arrival bound for tsk, and (2) it is a monotonic function that equals 0 for the empty interval delta = 0.
Let tsk be any task in ts that is to be analyzed.
  Variable tsk : Task.
  Hypothesis H_tsk_in_ts : tsk \in ts.

Recall that we assume sequential readiness, i.e., jobs of the same task are executed in order of their arrival.
  #[local] Instance sequential_readiness : JobReady _ _ :=
    sequential_ready_instance arr_seq.

Next, consider any ideal uniprocessor schedule of this arrival sequence.
Finally, we assume that the schedule is work-conserving ...
... and that it respects a reflexive and transitive fixed-priority scheduling policy FP.

Computation of the Fixpoints

In the following, we introduce the bound on the maximum busy-window length L and the response-time bound R and assume that they have been are calculated using the tools provided by util.fixpoint.
Let h denote the horizon for the fixpoint search, i.e., an upper bound on the maximum relevant fixpoint. Practically speaking, this is the threshold at which the fixpoint search is aborted and ends in failure. Since we assume in the following that the fixpoint search terminated successfully, it implies that h was chosen to be "sufficiently large"; it may hence be safely ignored in the following.
  Variable h : nat.

We let L denote the bound on the maximum busy-window length ...
  Variable L : duration.

... and assume that it has been found by means of a successful fixpoint search.
Recall the notion of the search space of the RTA for fixed-priority scheduling.
We let R denote tsk's response-time bound ...
  Variable R : duration.

... and assume that it has been found by means of finding the maximum among the fixpoints for each element in the search space with regard to the following recurrence function.
  Let recurrence A F := task_request_bound_function tsk (A + ε)
                        + total_ohep_request_bound_function_FP ts tsk (A + F)
                        - A.
  Hypothesis H_R_is_max_fixpoint :
    Some R = find_max_fixpoint L is_in_search_space recurrence h.

Correctness of the Response-Time Bound

Using the lemmas from util.fixpoints, we can show that all preconditions of the general fully preemptive fixed-priority RTA theorem are met.