christoph/fail
1
Fork 0
Code Actions Packages Releases Activity

globally rename Fail* to FAIL*

Browse Source 
Change-Id: Ief2cb687cc69dd92c2e04f9314f0f1347e0a84ed
This commit is contained in:
Horst Schirmeier
2016-03-15 23:38:49 +01:00
parent 94a56c43c8
commit d3d2faf680
43 changed files with 120 additions and 121 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/experiments/l4-sys/experiment.hpp
View File

@ -152,7 +152,7 @@ private:
/**
* Adds the value of the config file to the parameter list and
* parse the parameter list. This function makes use of the
* CommandLine Parser from the fail* framework.
* CommandLine Parser from the FAIL* framework.
*/
void parseOptions(L4SysConfig&);

10
src/experiments/l4-sys/manual.tex
View File

@ -34,7 +34,7 @@ you to read this whole document before investigating further.
\section{Overview}
This is the user manual of the \lfs{} generic system test framework.
The framework builds on Fail* and provides means to perform fault injection
The framework builds on FAIL* and provides means to perform fault injection
experiments for applications running on top of the Fiasco.OC/L4Re
microkernel-based operating system as well as the underlying microkernel.
@ -47,13 +47,13 @@ microkernel-based operating system as well as the underlying microkernel.
\noindent \lfs{} currently works for x86/32 running in Fail/Bochs only.
This is partly due to some issues with timing --- as soon as a valid model of
time in the target emulator as well as an assembler/disassembler functionality
in the Fail* framework are established, I would recommend a backend change, as
in the FAIL* framework are established, I would recommend a backend change, as
Bochs' reliability is very limited.
\section{Framework Setup}
To prepare a fault injection campaign you will first need to configure and
build Fail* itself. This process is described in \texttt{doc/how-to-build.txt}.
build FAIL* itself. This process is described in \texttt{doc/how-to-build.txt}.
The following CMake flags need to be set:
\begin{itemize}[itemsep=0em]
@ -94,7 +94,7 @@ in Bochs.
\section{Client Setup}
Now that we have Fail* and the L4Re setup running, we can prepare our fault
Now that we have FAIL* and the L4Re setup running, we can prepare our fault
injection campaign. This requires three (+ one optional) steps:
\begin{enumerate}[topsep=0em,itemsep=0em]
\item \emph{OPTIONAL:} If we want to perform a campaign that only targets
@ -203,7 +203,7 @@ be added to specify the host name or ip addr. of the machine running
Each experiment client processes exactly one experiment
and exits. To complete your campaign, you should use the \verb+client.sh+
script in the \texttt{scripts} subdirectory of Fail*.
script in the \texttt{scripts} subdirectory of FAIL*.
\section{Get your results}