From: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
To: ltp-list@lists.sourceforge.net
Cc: ltp-coverage@lists.sourceforge.net, Thomas.Cleary@faa.gov
Subject: Re: [LTP] [Ltp-coverage] Linux Kernel code coverage
Date: Thu, 05 May 2011 12:22:10 +0200 [thread overview]
Message-ID: <4DC27A52.6000906@linux.vnet.ibm.com> (raw)
In-Reply-To: <OFCE99A449.0BE9809D-ON85257885.006ACE3C-85257885.006BBD47@faa.gov>
Hi,
I'm not aware of any current activities to measure Linux kernel code
coverage of the LTP test suite. I'm forwarding your mail to the main LTP
mailing list - maybe one of the test suite maintainers or contributors
has more information.
Regards,
Peter Oberparleiter
On 03.05.2011 21:36, Thomas.Cleary@faa.gov wrote:
> I see a nice 2008 brief on the Linux Kernel code coverage statistics, was
> there any update to this brief on the current LTP test cases "statement
> coverage"?
>
> What is your assessment on the feasibility of re-engineering Kernel
> 2.6.18-194els? i.e. in the context of DO-178/278 to development high&low
> level requirements and ensure>%90+ statement coverage?
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
parent reply other threads:[~2011-05-05 10:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <OFCE99A449.0BE9809D-ON85257885.006ACE3C-85257885.006BBD47@faa.gov>]
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=4DC27A52.6000906@linux.vnet.ibm.com \
--to=oberpar@linux.vnet.ibm.com \
--cc=Thomas.Cleary@faa.gov \
--cc=ltp-coverage@lists.sourceforge.net \
--cc=ltp-list@lists.sourceforge.net \
/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