From: Daniel Veillard <veillard@redhat.com>
To: kyle@silverbeach.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Idea: Qemu as test coverage tool for kernels
Date: Mon, 30 Jan 2006 04:37:52 -0500 [thread overview]
Message-ID: <20060130093752.GC23578@redhat.com> (raw)
In-Reply-To: <200601292208.26827.kyle@silverbeach.net>
On Sun, Jan 29, 2006 at 10:08:26PM -0800, Kyle Hayes wrote:
> On Saturday 28 January 2006 04:26, Blue Swirl wrote:
> > Hi,
> >
> > Qemu's system emulators could be modified to output information about
> > the code areas which have been executed by the virtual CPU. The output
> > could then be used in standard test coverage tools. The benefit would be
> > the ability to get kernel-level coverage data.
>
> You might want to look a valgrind. The KDE project uses it heavily for
> memory leak and other types of problem detection. It is a sort of
> intermediate step between an interpreter and Qemu. I'm not sure where it
> lives, but Google should find it.
Another option might be SystemTap, by activating and counting all probes
and then generating coverage maps from the output, might be simpler to
actually set-up, though I have no idea of the resulting impedance of activating
all probes in a running kernel:
http://sourceware.org/systemtap/
http://www.redhat.com/magazine/011sep05/features/systemtap/
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
prev parent reply other threads:[~2006-01-30 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 12:26 [Qemu-devel] Idea: Qemu as test coverage tool for kernels Blue Swirl
2006-01-29 5:26 ` Mulyadi Santosa
2006-01-29 10:14 ` Blue Swirl
2006-01-30 6:08 ` Kyle Hayes
2006-01-30 9:37 ` Daniel Veillard [this message]
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=20060130093752.GC23578@redhat.com \
--to=veillard@redhat.com \
--cc=kyle@silverbeach.net \
--cc=qemu-devel@nongnu.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 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.