All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: ltp-list <ltp-list@lists.sourceforge.net>,
	ltp-coverage <ltp-coverage@lists.sourceforge.net>,
	Peter Oberparleiter <oberpar@linux.vnet.ibm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Deepak Saxena <dsaxena@linaro.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	fhrbata@redhat.com, Arnd Bergmann <arnd.bergmann@linaro.org>,
	Mark Brown <mark.brown@linaro.org>,
	Milosz Wasilewski <milosz.wasilewski@linaro.org>
Subject: Re: [LTP] How to get the Linux kernel coverage data on ARM arch when I run LTP test?
Date: Mon, 3 Mar 2014 16:21:11 +0100	[thread overview]
Message-ID: <CAHTX3dLrfW_Hbqx_-vEfcHGCh7c4n=Hs1OATfvjJ9UEaxJTCaQ@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYv9+Fhyz=nVZQZXxLU0YMTJadfr1XVVVb9P=inEfUaDuA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1305 bytes --]

HI,


2014-02-18 15:30 GMT+01:00 Naresh Kamboju <naresh.kamboju@linaro.org>:

> On 14 February 2014 15:13, Peter Oberparleiter
> <oberpar@linux.vnet.ibm.com> wrote:
> > On 14.02.2014 10:02, Naresh Kamboju wrote:
> >> root@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@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
>
> It is working !!!
> LTP executed on linux-linaro build on vexpress-tc2 target.
> Please find results obtained
> http://people.linaro.org/~naresh.kamboju/linux-linaro-coverage-by-ltp/
>
> The plan is to run all linaro test suite and to get coverage date.


Have you already run it? Are these test cases available?

Thanks,
Michal

[-- Attachment #1.2: Type: text/html, Size: 2167 bytes --]

[-- Attachment #2: Type: text/plain, Size: 451 bytes --]

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2014-03-03 15:46 UTC|newest]

Thread overview: 13+ 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:02 ` [LTP] " Naresh Kamboju
2014-02-14  9:02 ` Naresh Kamboju
2014-02-14  9:43 ` [LTP] " Peter Oberparleiter
2014-02-14  9:43   ` Peter Oberparleiter
2014-02-14  9:43   ` Peter Oberparleiter
2014-02-18 14:30   ` Naresh Kamboju
2014-02-18 14:30     ` Naresh Kamboju
2014-02-18 14:30     ` Naresh Kamboju
2014-03-03 15:21     ` Michal Simek [this message]
2014-04-04 11:00       ` Naresh Kamboju
2014-04-04 11:00         ` Naresh Kamboju
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='CAHTX3dLrfW_Hbqx_-vEfcHGCh7c4n=Hs1OATfvjJ9UEaxJTCaQ@mail.gmail.com' \
    --to=monstr@monstr.eu \
    --cc=arnd.bergmann@linaro.org \
    --cc=dsaxena@linaro.org \
    --cc=fhrbata@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltp-coverage@lists.sourceforge.net \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=mark.brown@linaro.org \
    --cc=milosz.wasilewski@linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=oberpar@linux.vnet.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.