From: oberpar@linux.vnet.ibm.com (Peter Oberparleiter)
To: linux-arm-kernel@lists.infradead.org
Subject: [LTP] How to get the Linux kernel coverage data on ARM arch when I run LTP test?
Date: Fri, 14 Feb 2014 10:43:06 +0100 [thread overview]
Message-ID: <52FDE52A.4070002@linux.vnet.ibm.com> (raw)
In-Reply-To: <CA+G9fYuT4TSs=3j6K9zztsTgFNVp2YG6JT-2Q_L==1P5G+SBew@mail.gmail.com>
On 14.02.2014 10:02, Naresh Kamboju wrote:
> root at linaro-developer:/tmp/linux-linaro-3.13-2014.01# gcov kernel/gcov/base.c -o
> /sys/kernel/debug/gcov/tmp/linux-linaro-3.13-2014.01/kernel/gcov/
> File 'kernel/gcov/base.c'
> Lines executed:43.18% of 44
> Creating 'base.c.gcov'
>
> root at linaro-developer:/tmp/linux-linaro-3.13-2014.01#
>
> The above experiment gives coverage of a single file base.c when i run
> gcov manually.
> Is there any way to get Linux kernel coverage of all files after
> running LTP test cases ?
1. Reset coverage data: lcov -z
2. Run LTP (or any other test case)
3. Capture coverage data: lcov -c -o coverage.info
4. Generate HTML output: genhtml coverage.info -o out
5. View HTML output: <browser> out/index.html
More information on lcov can be found on the page behind the second URL
your quoted in your mail.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on System z Development - IBM Germany
next prev parent reply other threads:[~2014-02-14 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 9:02 How to get the Linux kernel coverage data on ARM arch when I run LTP test? Naresh Kamboju
2014-02-14 9:43 ` Peter Oberparleiter [this message]
2014-02-18 14:30 ` [LTP] " Naresh Kamboju
[not found] ` <CAHTX3dLrfW_Hbqx_-vEfcHGCh7c4n=Hs1OATfvjJ9UEaxJTCaQ@mail.gmail.com>
2014-04-04 11:00 ` Naresh Kamboju
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=52FDE52A.4070002@linux.vnet.ibm.com \
--to=oberpar@linux.vnet.ibm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).