Lines Matching full:gcov

1 Using gcov with the Linux kernel
4 gcov profiling kernel support enables the use of GCC's coverage testing
6 is exported in gcov-compatible format via the "gcov" debugfs directory.
8 directory and use gcov with the ``-o`` option as follows (requires root)::
11     # gcov -o /sys/kernel/debug/gcov/tmp/linux-out/kernel spinlock.c
14 in the current directory. In addition, graphical gcov front-ends such
25 .. _gcov: https://gcc.gnu.org/onlinedocs/gcc/Gcov.html
81 The gcov kernel support creates the following files in debugfs:
83 ``/sys/kernel/debug/gcov``
84 	Parent directory for all gcov-related files.
86 ``/sys/kernel/debug/gcov/reset``
90 ``/sys/kernel/debug/gcov/path/to/compile/dir/file.gcda``
91 	The actual gcov data file as understood by the gcov
94 ``/sys/kernel/debug/gcov/path/to/compile/dir/file.gcno``
95 	Symbolic link to a static data file required by the gcov
104 module unload time. The gcov mechanism provides a means to collect
122 The gcov kernel profiling infrastructure is designed to work out-of-the
125 must be made, depending on where the gcov tool is used:
129 a) gcov is run on the TEST machine
131     The gcov tool version on the test machine must be compatible with the
150 b) gcov is run on the BUILD machine
155     from the gcov directory in sysfs:
159     These files can be copied to any location on the build machine. gcov
169       [user@build] gcov -o /tmp/coverage/tmp/out/init main.c
175 GCC and LLVM gcov tools are not necessarily compatible. Use gcov_ to work with
178 .. _gcov: https://gcc.gnu.org/onlinedocs/gcc/Gcov.html
181 Build differences between GCC and Clang gcov are handled by Kconfig. It
182 automatically selects the appropriate gcov format depending on the detected
218 (see :ref:`Separated build and test machines a. <gcov-test>`):
251 (see :ref:`Separated build and test machines b. <gcov-build>`):
258     GCDA=/sys/kernel/debug/gcov