Lines Matching defs:Barrelfish
44 \author{Barrelfish project}
65 The tracing framework in Barrelfish consists of three major components:
69 \item Bfscope (a Barrelfish program).
81 \chapter{Design and Implementation of the Tracing Framework in Barrelfish}
85 The tracing framework inside of Barrelfish existed already before this project
94 implemented in Barrelfish, i.e.~the actual functionality that developers use in
99 we changed the existing Barrelfish application Bfscope in such a way, that it
103 The typical lifecycle of using the tracing framework in Barrelfish looks like
147 tracing framework, and chips is the Barrelfish nameserver. The grey boxes
166 in Barrelfish\footnote{Currently there exist 16 different Subsystems.}.
191 \caption{Representation of a single trace event in memory in Barrelfish.}
203 specific language for error codes in Barrelfish (called fugu) a lot -- due to
216 inside of Barrelfish, but Aquarium will use the textual description to display
243 Parsing and interpreting of pleco files is part of the Barrelfish build process,
246 Barrelfish toolchain can be seen in Figure \ref{fig:pleco-process}. Note that
256 Barrelfish.}
264 Barrelfish source code, this file can be included with the statement:
355 single instance of Barrelfish on multiple machines, and in this case the
389 process itself. An application where this is currently necessary in Barrelfish
420 correctness, but it can heavily skew the flow of events in the Barrelfish as a
425 Bfscope is a Barrelfish program that enhances the functionality of the tracing
427 that the tracing in the Barrelfish code itself runs independently of Bfscope --
430 Barrelfish OS, using a TCP connection and to get the trace logs directly onto
432 commands in Barrelfish will automatically be redirected onto the network, and
498 \item Reading trace log data directly from a Barrelfish machine, using a
505 been generated during the build process of Barrelfish, based on the pleco file.
694 This chapter describes how to use the Tracing framework in Barrelfish.
746 Assuming you have network hardware that works with Barrelfish you can also
747 connect Aquarium 2 directly to the tracing infrastructure inside Barrelfish. The
748 current default port for that is \verb!6666!. If your Barrelfish and Aquarium 2
749 machines are on the same subnet you can just connect to the Barrelfish machine's
751 that can talk to the Barrelfish machines you can use ssh port-forwarding to
752 connect Aquarium 2 to Barrelfish directly using the ssh invocation below.
755 ssh -L 6666:\textless IP of Barrelfish machine\textgreater:6666 \textless ssh-machine\textgreater
763 Barrelfish. The analysis tool Aquarium is not analyzed for its performance, as
765 the consume the data on live mode from a Barrelfish machine, it is considered to
767 inside of Barrelfish; This stems from the fact that if you do not want to
770 tracing framework in Barrelfish, it is on one hand less easy to disable -- once
778 the entire runtime of Barrelfish, as the only used buffers are allocated at