Skip to content
Snippets Groups Projects
  1. Feb 18, 2025
  2. Feb 07, 2024
  3. Jan 23, 2024
  4. Nov 24, 2023
  5. Jul 07, 2023
  6. Jun 29, 2023
  7. Jun 13, 2023
  8. Apr 19, 2023
  9. Mar 29, 2023
  10. Mar 01, 2023
  11. Jan 20, 2023
    • Sergey Bozhko's avatar
      generalize abstract RTA · d4aab506
      Sergey Bozhko authored
      Changes:
      
      * This commit generalises aRTA to "multi-stage" aRTA. The general idea
      is explained in file [analysis/abstract/abstract_rta.v]. Short idea is
      that the fixpoint equation can be extended to a sequence of fixpoint
      equations. Solution to an equation can be used in later fixpoints. This
      way one can support move expressive models of execution. The prior
      version of aRTA (applicable to ideal uni-processors) is now an
      instantiation of the new RTA theorem.
      
      * Interference and Interfering workload are now type-classes. Note that
      this changes files in directory [results], since [Variables] were
      replaced with [Instance] declarations.
      
      * IBF supports arbitrary parameters (not just relative arrival time).
      IBF parametrised by the relative arrival time is not expressive enough
      to support restricted-supply analysis. It was generalized to support a
      larger class of parameters
      
      * Rename [run to completion] file into [lower bound on service]. The
      file was slightly generalized, now  it derives a lower bound on any
      pre-defined amount of service.
      
      * Generalize instantiations of interference and interfering workload.
      Now, the definitions do not directly destruct the processor state.
      Also, definitions for these functions have been made opaque.
      d4aab506
  12. Aug 25, 2022
  13. Jul 14, 2022
    • Kimaya Bedarkar's avatar
      aRTA clean-up · 98612039
      Kimaya Bedarkar authored and Björn Brandenburg's avatar Björn Brandenburg committed
      * The lemmas concerning the correctness of interference and interfering
        workload for JLFP policies are independent of specific scheduling
        policies. Therefore, these lemmas have been proved in the
        `ideal_jlfp_rta` for any general `JLFP` policies satisfying certain
        conditions.
      * The precondition `job_of_task j tsk` in the work-conservation
        definition was unnecessary. This has been removed.
      * Two new lemmas have been added to the global facts database. This led
        to the simplification of some proofs.
      * Fixed one broken comment in `model.task.sequentiality`.
      * Simplified one proof in `ideal_jlfp_rta` since it kept breaking due to
        use of auto-generated names. This required creating one new file -
        `analysis.facts.busy_interval.quiet_time`. Currently, this file
        contains just one lemma that is used in the `ideal_jlfp_rta` file.
      98612039
  14. Apr 19, 2022
  15. Feb 17, 2022
  16. Feb 16, 2022
  17. Nov 02, 2021
  18. Oct 07, 2021
  19. Sep 30, 2021
    • Sergey Bozhko's avatar
      relax assumption in aRTA · 29556ed5
      Sergey Bozhko authored
      Currently, aRTA required [F] to be solution of equation
      [A + F = task_rtct + IBF A (A + F)], this commit relaxes
      this assumption to [A + F >= task_rtct + IBF A (A + F)]
      29556ed5
  20. Sep 29, 2021
  21. Sep 08, 2021
  22. Dec 11, 2020
    • Sergey Bozhko's avatar
      optimize names for run-to-completion threshold functions · c14a8266
      Sergey Bozhko authored and Björn Brandenburg's avatar Björn Brandenburg committed
      The names for job's and task's run-to-completion
      threshold functions are so long that it often gets
      in the way of writing theorems and proofs. As
      a compromise between verbosity and convenience it
      was decided to rename [task_run_to_completion_threshold]
      to [task_rtct] and [job_run_to_completion_threshold]
      to [job_rtct].
      c14a8266
  23. Sep 23, 2020
    • Sergey Bozhko's avatar
      Add [arrives_in] to [sequential_tasks] definition · 33a48458
      Sergey Bozhko authored
      Note that the prior definition of [sequential_tasks]
      did not differentiate between a job coming from the
      arrival sequence and any other job. However, all
      computable properties (such as [job_respects_task_rtc,
      valid_preemption_model, arrivals_have_valid_job_costs,
      all_deadlines_of_arrivals_met]) are stated exclusively
      for jobs from the arrival sequence. In order to make
      the definition of [sequential_tasks] compatible with
      computable properties, we add preconditions
      [arrives_in arr_seq j1] and [arrives_in arr_seq j2].
      33a48458
  24. Apr 01, 2020
  25. Mar 10, 2020
  26. Dec 20, 2019
  27. Dec 19, 2019
  28. Dec 10, 2019
    • Sergey Bozhko's avatar
      address spell-checking issues in analysis · d1f8192c
      Sergey Bozhko authored and Björn Brandenburg's avatar Björn Brandenburg committed
      d1f8192c
    • Björn Brandenburg's avatar
      re-organization of the analysis module, part 1 · 064a1c75
      Björn Brandenburg authored
      This is not yet the final organization, but already an improvement.
      
      Move main high-level results to separate top-level `results` module.
      Rationale: Let's make it very clear where to find the main, high-level
      results in Prosa, and at the same time let's declutter the analysis
      namespace.
      
      Other notable change, apart from moving files around:
      
      - move two key analysis definitions to analysis.definitions
      - split RBF definition and facts into separate files
      - move facts about ideal schedule to ideal_schedule.v
      064a1c75
  29. Dec 03, 2019
Loading