| [pok-devel] [30] *doc/userguide/configuration.tex |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/pok-devel Archives
]
Revision: 30
Author: julien
Date: 2012-03-28 23:17:23 +0200 (Wed, 28 Mar 2012)
Log Message:
-----------
*doc/userguide/configuration.tex
libpok/include/protocols/ceasar.h
- Fix spelling errors
Modified Paths:
--------------
trunk/doc/userguide/configuration.tex
trunk/libpok/include/protocols/ceasar.h
Modified: trunk/doc/userguide/configuration.tex
===================================================================
--- trunk/doc/userguide/configuration.tex 2012-02-18 22:47:47 UTC (rev 29)
+++ trunk/doc/userguide/configuration.tex 2012-03-28 21:17:23 UTC (rev 30)
@@ -22,7 +22,7 @@
must write it carefully since a mistake can have significant impacts in terms of
safety or security.
-Most of the time, the C configuration code will be maccros in global variables.
+Most of the time, the C configuration code will be macros in global variables.
The purpose of this chapter is to detail each variable. If you use generated
code, the configuration code is mostly generated in \texttt{deployment.c} and
\texttt{deployment.h} files.
@@ -38,7 +38,7 @@
AADL models. Indeed, ARINC653 XML files do not contain enough information to
generate the whole configuration and is not sufficient to generate the
configuration of partitions. However, this is a good way to have basic
-configuration files that can be improved by manual edition.
+configuration files that can be improved by manual editing.
The tool is located in the \texttt{misc} directory of POK releases. You can use
it as it:
@@ -52,7 +52,7 @@
\section{Common configuration}
-The following maccros can be defined for both partitions and kernel:
+The following macros can be defined for both partitions and kernel:
\begin{itemize}
\item
\texttt{POK\_GENERATED\_CODE}: specify that the code compiled has been
@@ -63,18 +63,18 @@
\section{Kernel configuration}
\subsection{Services activation}
- You can define which functionnalities you want in the kernel by defining
- some maccros. Depending on which maccro you define, it will add services and
- functionnalities in your kernel. It was made to make a very tight kernel and
+ You can define which capabilities you want in the kernel by defining
+ some macros. Depending on which maccro you define, it will add services and
+ capabilities in your kernel. It was made to make a very tight kernel and
ease verification/certification efforts.
- When you use code generation functionnalities, these declarations are
+ When you use code generation capabilities, these declarations are
automatically created in the \texttt{deployment.h} file.
\begin{itemize}
\item
\texttt{POK\_NEEDS\_PARTITIONS} maccro indicates that you need partitioning
- services. It implies that you define configuration maccros and
+ services. It implies that you define configuration macros and
variables for the partitioning service.
\item
\texttt{POK\_NEEDS\_SCHED} maccro specifies that you need the
@@ -157,7 +157,7 @@
\subsubsection{Number of nodes}
The \texttt{POK\_CONFIG\_NB\_NODES} specifies the number of nodes in the
distributed system if you use a such architecture. It is useful if you
- have more than one node and use network functionnalities.
+ have more than one node and use network capabilities.
\begin{verbatim}
#define POK_CONFIG_PARTITIONS_NTHREADS {2,2,2,4}
@@ -192,7 +192,7 @@
\subsubsection{Scheduler of partitions (level 0 of scheduling)}
- The scheduling of partitions is specified with several maccros.
+ The scheduling of partitions is specified with several macros.
The \texttt{POK\_CONFIG\_SCHEDULING\_NBSLOTS} specifies the number of time
frames allocated for partitions execution.
@@ -280,7 +280,7 @@
The identifier of the current node is specified with the
\texttt{POK\_CONFIG\_LOCAL\_NODE} maccro.
- When you use code generation functionnalities, this declaration is
+ When you use code generation, this declaration is
automatically created in the \texttt{deployment.h} file.
\subsubsection{Number of global ports}
@@ -288,7 +288,7 @@
with the \texttt{POK\_CONFIG\_NB\_GLOBAL\_PORTS}. It indicates the number of
global ports in the system.
- When you use code generation functionnalities, this declaration is
+ When you use code generation, this declaration is
automatically created in the \texttt{deployment.h} file.
\subsubsection{Number of local ports}
@@ -296,7 +296,7 @@
using the \texttt{POK\_CONFIG\_NB\_PORTS} maccro. It specifies the number of
ports on the local node.
- When you use code generation functionnalities, this declaration is
+ When you use code generation, this declaration is
automatically created in the \texttt{deployment.h} file.
\subsubsection{Local ports identifiers}
@@ -307,7 +307,7 @@
Note that this enum declaration specifies the local ports of the current node
and consequently, it is dependent on each node communication requirements.
- When you use code generation functionnalities, this declaration is
+ When you use code generation, this declaration is
automatically created in the \texttt{deployment.h} file.
There is an example of a such enum
@@ -327,7 +327,7 @@
\texttt{pok\_port\_identifier\_t}. This enum declaration must be \textbf{THE SAME}
on all node of the distributed system.
- When you use code generation functionnalities, this declaration is
+ When you use code generation, this declaration is
automatically created in the \texttt{deployment.h} file.
There is an example of a such enum declaration:
@@ -350,7 +350,7 @@
must be in this enum declaration. This enum declaration is \textbf{THE SAME} on
all nodes of the distributed system.
- When you use code generation functionnalities, this declaration is
+ When you use code generation, this declaration is
automatically created in the \texttt{deployment.h} file.
There is an example of a such declaration
@@ -376,7 +376,7 @@
Here, the first local port of the current node corresponds to the
\texttt{node1\_partition\_secret\_outgoing} global port.
- When you use code generation functionnalities, this declaration is
+ When you use code generation, this declaration is
automatically created in the \texttt{deployment.c} file.
@@ -431,7 +431,7 @@
node1_partition_unclassified_outgoing_global};
\end{verbatim}
- When you use code generation functionnalities, this declaration is
+ When you use code generation, this declaration is
automatically created in the \texttt{deployment.c} file.
@@ -457,7 +457,7 @@
invalid_local_port};
\end{verbatim}
- When you use code generation functionnalities, this declaration is
+ When you use code generation, this declaration is
automatically created in the \texttt{deployment.c} file.
\subsubsection{Location of each global port}
@@ -473,7 +473,7 @@
{0,0,0,1,1,1};
\end{verbatim}
- When you use code generation functionnalities, this declaration is
+ When you use code generation, this declaration is
automatically created in the \texttt{deployment.c} file.
@@ -502,7 +502,7 @@
associated with them.
\end{enumerate}
- When you use code generation functionnalities, this declaration is
+ When you use code generation, this declaration is
automatically created in the \texttt{deployment.c} file.
@@ -521,7 +521,7 @@
"node1_partition_unclassified_outgoing"};
\end{verbatim}
- When you use code generation functionnalities, this declaration is
+ When you use code generation, this declaration is
automatically created in the \texttt{deployment.c} file.
\subsubsection{Specify port usage for each partition}
@@ -561,13 +561,13 @@
node1_partition_unclassified_partport};
\end{verbatim}
- When you use code generation functionnalities, this declaration is
+ When you use code generation, this declaration is
automatically created in the \texttt{deployment.c} file.
\section{Libpok (partition runtime)}
\section{Configuration}
- You define the configuration policy by defining some C-style maccros. There
- are the list of useful maccros:
+ You define the configuration policy by defining some C-style macros. There
+ are the list of useful macros:
\begin{itemize}
\item
\texttt{POK\_CONFIG\_NB\_THREADS}: specify the number of threads
@@ -601,13 +601,13 @@
\end{itemize}
\section{Services activation}
- To activate \textit{libpok} services, you must define some maccros. By
+ To activate \textit{libpok} services, you must define some macros. By
default, you don't have any services. You activate service by defining
macros. Thus, it ensures that each partition contains only required services
and avoid any memory overhead in partitions.
- These maccros have the form \texttt{POK\_NEEDS\_...}. There is a list of
- these maccros:
+ These macros have the form \texttt{POK\_NEEDS\_...}. There is a list of
+ these macros:
\begin{itemize}
\item
\texttt{POK\_NEEDS\_RTL8029}: activate the functions of the device
@@ -644,7 +644,7 @@
\item
\texttt{POK\_NEEDS\_ALLOCATOR} : activate the memory allocator of the
partition. This service can be configured with
- \texttt{POK\_CONFIG\_ALLOCATOR...} maccros.
+ \texttt{POK\_CONFIG\_ALLOCATOR...} macros.
\item
\texttt{POK\_NEEDS\_ARINC653\_PROCESS}: activate the process service of
the ARINC653 layer.
Modified: trunk/libpok/include/protocols/ceasar.h
===================================================================
--- trunk/libpok/include/protocols/ceasar.h 2012-02-18 22:47:47 UTC (rev 29)
+++ trunk/libpok/include/protocols/ceasar.h 2012-03-28 21:17:23 UTC (rev 30)
@@ -27,7 +27,7 @@
* This is a very basic crypto protocol that just
* change the order of bytes in data. There is no
* public/private key, the algorithm is known
- * by the attaker so that it's a very weak crypto
+ * by the attacker so that it's a very weak crypto
* protocol.
* Interested people can gather more information
* about this protocol on: