All of lore.kernel.org
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>,
	Milosz Wasilewski <milosz.wasilewski@linaro.org>
Cc: Arnd Bergmann <arnd.bergmann@linaro.org>,
	fhrbata@redhat.com, Paul Larson <paul.larson@canonical.com>,
	ltp-list <ltp-list@lists.sourceforge.net>,
	ltp-coverage <ltp-coverage@lists.sourceforge.net>,
	Mark Brown <mark.brown@linaro.org>,
	"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>
Subject: Re: [LTP] How to get the Linux kernel coverage data on ARM arch when I run LTP test?
Date: Tue, 18 Feb 2014 20:00:21 +0530	[thread overview]
Message-ID: <CA+G9fYv9+Fhyz=nVZQZXxLU0YMTJadfr1XVVVb9P=inEfUaDuA@mail.gmail.com> (raw)
In-Reply-To: <52FDE52A.4070002@linux.vnet.ibm.com>

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.

Peter Oberparleiter,
Thank you very much for your help.

Best regards
Naresh Kamboju

>
> 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
>

WARNING: multiple messages have this Message-ID (diff)
From: naresh.kamboju@linaro.org (Naresh Kamboju)
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: Tue, 18 Feb 2014 20:00:21 +0530	[thread overview]
Message-ID: <CA+G9fYv9+Fhyz=nVZQZXxLU0YMTJadfr1XVVVb9P=inEfUaDuA@mail.gmail.com> (raw)
In-Reply-To: <52FDE52A.4070002@linux.vnet.ibm.com>

On 14 February 2014 15:13, Peter Oberparleiter
<oberpar@linux.vnet.ibm.com> wrote:
> 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

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.

Peter Oberparleiter,
Thank you very much for your help.

Best regards
Naresh Kamboju

>
> 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
>

WARNING: multiple messages have this Message-ID (diff)
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>,
	Milosz Wasilewski <milosz.wasilewski@linaro.org>
Cc: ltp-list <ltp-list@lists.sourceforge.net>,
	ltp-coverage <ltp-coverage@lists.sourceforge.net>,
	fhrbata@redhat.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Deepak Saxena <dsaxena@linaro.org>,
	Mark Brown <mark.brown@linaro.org>,
	Arnd Bergmann <arnd.bergmann@linaro.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [LTP] How to get the Linux kernel coverage data on ARM arch when I run LTP test?
Date: Tue, 18 Feb 2014 20:00:21 +0530	[thread overview]
Message-ID: <CA+G9fYv9+Fhyz=nVZQZXxLU0YMTJadfr1XVVVb9P=inEfUaDuA@mail.gmail.com> (raw)
In-Reply-To: <52FDE52A.4070002@linux.vnet.ibm.com>

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.

Peter Oberparleiter,
Thank you very much for your help.

Best regards
Naresh Kamboju

>
> 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
>

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2014-02-18 14:30 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 [this message]
2014-02-18 14:30     ` Naresh Kamboju
2014-02-18 14:30     ` Naresh Kamboju
2014-03-03 15:21     ` Michal Simek
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='CA+G9fYv9+Fhyz=nVZQZXxLU0YMTJadfr1XVVVb9P=inEfUaDuA@mail.gmail.com' \
    --to=naresh.kamboju@linaro.org \
    --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=oberpar@linux.vnet.ibm.com \
    --cc=paul.larson@canonical.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.