All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kyle Hayes <kyle@silverbeach.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Idea: Qemu as test coverage tool for kernels
Date: Sun, 29 Jan 2006 22:08:26 -0800	[thread overview]
Message-ID: <200601292208.26827.kyle@silverbeach.net> (raw)
In-Reply-To: <BAY104-F59C47E86DB180621BD9EFFF170@phx.gbl>

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.

Best,
Kyle

  parent reply	other threads:[~2006-01-30  6:11 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 [this message]
2006-01-30  9:37   ` Daniel Veillard

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=200601292208.26827.kyle@silverbeach.net \
    --to=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.