doc/000-overview/Overview.tex

71 core runs a kernel which is called a "CPU driver". The CPU driver maintains
96 \section{CPU drivers}
99 called a \emph{CPU driver}.  Each core runs a separate instance of the
100 CPU driver, and there is no reason why these drivers have to be the
103 In a heterogeneous Barrelfish system, CPU drivers will be different
104 for each architecture.  However, even on a homogeneous machine, CPU
109 CPU drivers are single-threaded and non-preemptible.
111 with other cores.  CPU drivers can be thought of as serially executing
115 CPU driver executes a user-space task.
117 The functions of a CPU driver are to provide:
129 CPU drivers do not provide kernel threads, for two reasons.  Firstly,
136 CPU drivers schedule dispatchers.  The scheduling algorithm employed
137 by a given CPU driver binary is configurable at compile time, and two
166 When a CPU driver decides to run a dispatcher as a result of a
498   local CPU driver to deliver particular interrupt vectors to the
513 back to the CPU driver.
545 appropriate CPU driver, each core other than the bootstrap core has a
566 inter-core communication (since CPU drivers by design do not
586 it into a user-space process rather than amalgamating it with the CPU
592 (the CPU driver has no blocking operations), can be implemented using
594 hard to crash the CPU driver in Barrelfish, since it performs no
692 \item[kernel/] Source code for Barrelfish CPU drivers.
693 \item[kernel/include/] Header files internal to Barrelfish CPU drivers.
767 \item[x86\_64/kernel/] Intermediate build files for all the CPU
772   architecture.  The CPU driver is generally known as
843   represented in Barrelfish, both inside the CPU driver and from user