*: extend and refine structure

src/docs/parts/research_and_development/research_and_development.tex

@@ -0,0 +1,64 @@
+% // vim: set ft=tex:
+\chapter{Topic Refinement}
+- TODO: is this chapter required?
+
+\chapter{Derived Research Questions}
+
+\subsection{Definition Of Additional Analysis Rules To Extend Safety Checks}
+* TODO: How can Business Logical
+Examples: 
+* TLB needs to be reset on Task Change
+* Registers need to be 
+
+\subsubsection{Software Fault Isolation}
+* TODO: content from \cite{Balasubramanian2017}
+
+\subsection{More Detailed Research Questions}
+* Which language items help with managing memory?
+* How generic can the memory allocators be written?
+
+Guarantees to be statically checked:
+* Control access to duplicates in page tables
+* Tasks can't access unallocated (physical) memory
+* Tasks can't access other tasks memory
+
+\subsection{Interrupts}
+* https://software.intel.com/sites/default/files/managed/39/c5/325462-sdm-vol-1-2abcd-3abcd.pdf p. 2848
+
+\section{Software Tests}
+* TODO: describe that tests are mostly semantics as opposed to static checks being mostly syntactical and technical
+* TODO: They necessary in addition to static checks to cover the well-known use-cases and edge-cases. TODO: example?
+
+\chapter{Attempt Extend \gls{Linux} with \gls{Rust}}
+* TODO: describe Difficulties with the GPL Macros used Within Kernel Modules
+
+\chapter{Existing \gls{OS}-Development Projects Based On Rust}
+
+
+\section{Libraries}
+
+\subsection{Libfringe}
+* https://github.com/edef1c/libfringe
+
+\section{Systems}
+\subsection{intermezzOS}
+\subsection{Blog OS}
+\subsection{Redox}
+\subsection{Tock}
+
+\chapter{Introduce Preemptive \gls{OS}-Level Multitasking to \gls{imezzos}}
+
+\chapter{Result Generalization}
+
+\section{Low-Level Safe Abstractions in Rust}
+* TODO: Is the static analysis of hardware specific assembly code possible and useful at all?
+    * LLVM knows about the target and can potentially give hints about hardware specific instructions
+
+\section{Tracking \textit{'static}ally allocated Resources}
+
+\section{The Necessary Evils of \textit{unsafe}}
+
+\chapter{Result Evaluation}
+* TODO: repeat that rust *can* be used to increase safety in the OS, but it doesn't guarantee it per-se
+
+\chapter{Summary}