Lines Matching refs:Kernel
36 \item[Kernel patch] A patch to the Linux kernel which includes the
37 kernel event logging interfaces, and patches to areas within the block
38 layer to emit event traces. If you run a 2.6.17-rc1 or newer kernel,
41 \item[blktrace] A utility which transfers event traces from the kernel
51 The blktrace and blkparse utilities and associated kernel patch are provided
54 git://git.kernel.org/pub/scm/linux/kernel/git/axboe/blktrace.git bt
65 As noted above, the kernel patch along with the blktrace and blkparse utilities are stored in a git repository. One simple way to get going would be:
68 % git clone git://git.kernel.org/pub/scm/linux/kernel/git/axboe/blktrace.git bt
73 \subsection{\label{sec:patching}Patching and configuring the Linux kernel}
75 A patch for a \emph{specific Linux kernel} is provided in bt/kernel (where
77 detailed actual patching instructions for a Linux kernel is outside the
79 Note that you may skip this step, if you kernel is at least 2.6.17-rc1.
81 As an example, bt/kernel contains blk-trace-2.6.14-rc1-git-G2, download
94 At this point you should configure the Linux kernel for your specific
105 Install the new kernel (and modules\ldots) and reboot.
110 the mount point set up -- mounted on the directory /sys/kernel/debug.
116 % mount -t debugfs debugfs /sys/kernel/debug
123 debug /sys/kernel/debug debugfs default 0 0
335 The \emph{blktrace} utility extracts event traces from the kernel (via
341 \item blktrace receives data from the kernel in buffers passed up
344 to \emph{/sys/kernel/debug} -- this can be overridden with the \emph{-r}
537 must be copied to/from kernel buffers. Usually this can be fixed with
541 \item[m -- message] Text message generated via kernel call to
736 \newpage\section*{\label{sec:blktrace-kg}Appendix: blktrace Kernel Guide}
741 blktrace utilizes in the kernel to effect this. It is good background data
771 kernel routine invocable interfaces:
