Commit b04d1a8d authored by Daniel Latypov's avatar Daniel Latypov Committed by Shuah Khan
Browse files

Documentation: kunit: update kconfig options needed for UML coverage 



Recent changes have made it so the current set is not sufficient.
Namely, CONFIG_DEBUG_INFO is not being set even when explicitly asked.

Specifying a version of the debug info fixes this.
Pick CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT as an option that's
hopefully less fragile (esp. given we're tied to GCC 6 and lower).

Signed-off-by: default avatarDaniel Latypov <dlatypov@google.com>
Reviewed-by: default avatarDavid Gow <davidgow@google.com>
Tested-by: default avatarMaxime Ripard <maxime@cerno.tech>
Reviewed-by: default avatarBrendan Higgins <brendanhiggins@google.com>
Signed-off-by: default avatarShuah Khan <skhan@linuxfoundation.org>
parent cdebea69

Documentation/dev-tools/kunit/running_tips.rst

+2 −1
Original line number Diff line number Diff line
@@ -114,6 +114,7 @@ Instead of enabling ``CONFIG_GCOV_KERNEL=y``, we can set these options: 


	CONFIG_DEBUG_KERNEL=y

	CONFIG_DEBUG_INFO=y

	CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT=y

	CONFIG_GCOV=y
@@ -122,7 +123,7 @@ Putting it together into a copy-pastable sequence of commands: 
.. code-block:: bash



	# Append coverage options to the current config

	$ echo -e "CONFIG_DEBUG_KERNEL=y\nCONFIG_DEBUG_INFO=y\nCONFIG_GCOV=y" >> .kunit/.kunitconfig

	$ echo -e "CONFIG_DEBUG_KERNEL=y\nCONFIG_DEBUG_INFO=y\nCONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT=y\nCONFIG_GCOV=y" >> .kunit/.kunitconfig

	$ ./tools/testing/kunit/kunit.py run

	# Extract the coverage information from the build dir (.kunit/)

	$ lcov -t "my_kunit_tests" -o coverage.info -c -d .kunit/