From: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: ltp-coverage@lists.sourceforge.net,
Andrew Morton <akpm@linux-foundation.org>,
Sam Ravnborg <sam@ravnborg.org>,
Peter Oberparleiter <oberparleiter@googlemail.com>
Subject: [PATCH 0/7] gcov kernel support
Date: Mon, 19 May 2008 10:42:54 +0200 [thread overview]
Message-ID: <48313D8E.7020109@de.ibm.com> (raw)
This is version #2 of the gcov kernel support patch set (see further
below for an in-depth explanation). Patch base is 2.6.26-rc3.
Changes are mostly based on mailing list feedback:
* added more documentation
* moved gcov config menu to general setup
* renamed some structures and variables (removed _t, lowercase ctors)
* split mod versioning change into separate patch (3)
* split GCC_VERSION_LOWER into separate patch (2)
* split gcov core patch into two patches (5+6) for better readability
* absolute paths only used when CONFIG_GCOV_PROFILE is set
* fixed compile problem with CONFIG_MODULES=n
* fixed memory leak in gcov fs code
* more style changes
Patch overview:
[PATCH 1/7] kernel: call constructors
[PATCH 2/7] kernel: introduce GCC_VERSION_LOWER macro
[PATCH 3/7] kbuild: delay object file renaming during module versioning
[PATCH 4/7] seq_file: add function to write binary data
[PATCH 5/7] gcov: add gcov profiling infrastructure
[PATCH 6/7] kbuild: make source and include paths absolute
[PATCH 7/7] gcov: architecture specific compile flag adjustments
===
This set of patches enables the use of GCC's coverage testing tool
gcov [1] with kernel 2.6.25. Coverage data for the running kernel is
exported via debugfs in a gcov-compatible format. To get coverage
data for a specific file, simply use gcov with the -o option:
# gcov -o /sys/kernel/debug/gcov/tmp/linux-2.6.25/kernel spinlock.c
This will create source code files annotated with execution counts
in the current directory. In addition, graphical gcov front-ends such
as lcov [2] can be used to automate the process of collecting data
for the entire kernel and provide coverage overviews in HTML format.
Possible uses:
* debugging (has this line been executed at all?)
* test improvement (how do I change my test to cover these lines?)
* minimizing kernel configurations (do I need this option if the
associated code is never executed?)
Known issues:
* some architecture specific problems: the patch has been tested
successfully on s390 and i386. Known problems exist on x86_64 and
arm (to be investigated)
* GCC's profiling mechanism together with optimization sometimes
produces skewed data (see [1])
* GCC's profiling code assumes single-threaded execution
* gcov assumes that a program has finished when coverage data is
analyzed
Despite these issues, the data which can be obtained has been proven
to be sufficiently accurate for most practical uses.
History:
Hubertus Franke <frankeh@us.ibm.com> wrote the first version of this
patch around 2002. Since then it has been adapted to new versions of
the kernel and GCC with contributions by several people (see file
kernel/gcov/fs.c, write me if I missed anyone). Due to regular
requests, I rewrote the gcov-kernel patch from scratch so that it
would (hopefully) be fit for inclusion into the upstream kernel.
--
[1] http://gcc.gnu.org/onlinedocs/gcc/Gcov.html
[2] http://ltp.sourceforge.net/coverage/lcov.php
next reply other threads:[~2008-05-19 8:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 8:42 Peter Oberparleiter [this message]
2008-05-19 11:42 ` [PATCH 0/7] gcov kernel support Andi Kleen
2008-05-23 8:12 ` Andrew Morton
2008-05-23 11:06 ` Segher Boessenkool
2008-05-23 16:56 ` Andrew Morton
2008-05-23 21:52 ` Segher Boessenkool
2008-05-23 22:23 ` Andrew Morton
2008-05-27 8:32 ` Peter Oberparleiter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48313D8E.7020109@de.ibm.com \
--to=peter.oberparleiter@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-coverage@lists.sourceforge.net \
--cc=oberparleiter@googlemail.com \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox