Lines Matching refs:to
8 than a userspace, it can't automatically write coverage out to the filesystem,
9 so some extra steps are required to collect and process the data.
14 and the coverage build tends to exceed this limit.
22 instead has to provide some parts of the implementation itself.
26 formats do change occasionally, and this may involve adjustments to Xen.
27 While we do our best to keep up with these changes, Xen may not be compatible
40 The ``SYSCTL_coverage_op`` hypercall is used to interact with the coverage
44 The ``read`` subcommand can be used to obtain the raw coverage data::
48 This is toolchain-specific data and needs to be fed back to the appropriate
49 programs to post-process.
51 Alternatively, the ``reset`` subcommand can be used reset all counters back to
61 object file. The raw coverage data needs splitting to form the matching
64 An example of how to view the data is as follows. It uses ``lcov`` which is a
65 graphical frontend to ``gcov``.
67 * Obtain the raw coverage data from the test host, and pull it back to the
69 * Use ``xencov_split`` to extract the ``*.gcda`` files. Note that full build
70 paths are used by the tools, so splitting needs to output relative to ``/``.
71 * Use ``geninfo`` to post-process the raw data.
72 * Use ``genhtml`` to render the results as HTML.
86 An example of how to view the data is as follows.
88 * Obtain the raw coverage data from the test host, and pull it back to the
90 * Use ``llvm-profdata`` to post-process the raw data.
91 * Use ``llvm-cov show`` in combination with ``xen-syms`` from the build to