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
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 g
Why not just use Oprofile (oprofile.sf.net) or standard "readprofile"
tool for this?
I didn't know about that, but after a quick look I'd say Oprofile is doing
performance profiling (which could be done using Qemu as well), not test
coverage analysis. Also, the kernel in question needs to be p
Hi...
On Saturday 28 January 2006 19: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 abili
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.
Are there any other tools f
