From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1F3VXl-0000hn-OL for qemu-devel@nongnu.org; Mon, 30 Jan 2006 04:41:54 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1F3VXj-0000fx-OK for qemu-devel@nongnu.org; Mon, 30 Jan 2006 04:41:52 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F3VX2-0000Hv-G4 for qemu-devel@nongnu.org; Mon, 30 Jan 2006 04:41:08 -0500 Received: from [66.187.233.31] (helo=mx1.redhat.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1F3VVJ-0006tp-UR for qemu-devel@nongnu.org; Mon, 30 Jan 2006 04:39:22 -0500 Date: Mon, 30 Jan 2006 04:37:52 -0500 From: Daniel Veillard Subject: Re: [Qemu-devel] Idea: Qemu as test coverage tool for kernels Message-ID: <20060130093752.GC23578@redhat.com> References: <200601292208.26827.kyle@silverbeach.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200601292208.26827.kyle@silverbeach.net> Reply-To: veillard@redhat.com, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: kyle@silverbeach.net, qemu-devel@nongnu.org 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/