Linux Kernel Code Coverage BLOG

[Français][Deutsch]

Running an instrumented Linux Kernel on a Laptop for about a week

Friday, May 19th, LTP run this week

Had run the LTP testsuite on that kernel. I have pan/pan.c, this is the testdrive, to get an approximately per test report. A bit noisy, as this measures all in that timeframe the test runs, but if you are familiar with that, should be easy to find the useful information.

Friday, May 12th, per Directory summary

Having patched ctc2html in a way, that we have now additionally a report per directory, the HTML-Report was re-generated for that.

Friday, May 5th, 17% TER finally

Having finally increased my code coverage to 17%. The textual report for that is available as profile-final.txt.gz.
SUMMARY
=======

Number of monitored source files  : 1532
Number of source lines            : 1029307
Number of measurement points      : 252003
TER                               : 17% (multicondition)

Wednesday, May 3th, got 16% TER

Just wanted to note, that I have increased test effectivness ratio to 16%. The textual report for that is available as profile-2.txt.gz.

HTML Report available

The new HTML Report is available as /newCTCHTML/

Noon, Tuesday, May, 2nd, 2006

I have started last Friday afternoon running an almost complete instrumented Linux Kernel on my Laptop exclusivly. The machine runs fine, no notable performance decrease.

Current status, Tuesday, May 2nd, 2006:

SUMMARY
=======

Number of monitored source files  : 1532
Number of source lines            : 1029307
Number of measurement points      : 248294
TER                               : 15% (multicondition)

Not too bad, as many mostly unused modules where compiled, done regular work on it. By the way, as I started, I got about 13% coverage just after booting.

The (textual) Report is available as profile-1.txt.gz. HTML will follow.