adbrucker
/
lh-l4v
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
lh-l4v/spec/design
History
Gerwin Klein 0cf64b5498
READMEs: use run_tests consistently in READMEs (#622) 
Avoid mixing `isabelle`, `make`, and `run_tests` invocations.
Standardise on `run_tests` and mention `L4V_ARCH` each time to
indicate that you can and should set `L4V_ARCH`.

Signed-off-by: Gerwin Klein <gerwin.klein@proofcraft.systems>
 		2023-03-30 13:59:18 +11:00
..
m-skel proofs: updates for monad refactor 2023-02-09 11:46:55 +11:00
skel riscv machine+design+crefine: explicitly set pptrTop 2023-03-29 11:05:26 +11:00
Makefile design: more precise Makefile dependencies 2020-04-01 14:31:36 +11:00
README.md READMEs: use run_tests consistently in READMEs (#622) 2023-03-30 13:59:18 +11:00

README.md

The Executable Design Specification of seL4

l4v/spec/design/

This directory contains the Isabelle sources of the executable design specification for seL4.

Most theory files in this directory are tool-generated, do not edit!

The files here are also not particularly well suited for human consumption, it is recommended to directly read the corresponding Haskell code in seL4/haskell instead.

Top-Level Theory

The top-level theory file that draws the whole specification together is API_H, the top-level function in that theory is callKernel.

Similarly to the abstract specification, this top-level function is later in the proofs further wrapped in an automaton that describes system behaviour on this level of abstraction.

Building

The corresponding Isabelle session is ExecSpec. Build in l4v for the ARM architecture with

L4V_ARCH=ARM ./run_tests ExecSpec

Remarks

  • for regenerating the design spec from Haskell sources, go to directory l4v/ and run

     ./run_test haskell-translator

  • skeleton files that define which parts of which Haskell files get mapped to which Isabelle theories are found in the sub directories skel and m-skel for design and machine respectively.