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
The fact, that we can only reproduce frequencies up to half of
sampling frequency, has already been dealt with since the first patch
I posted (2006-01-18).
I chose to use a sample rate of 32000 Hz, which should be sufficient
for our purpose. So we can handle PIT count values down to 75.
P
On Saturday 28 January 2006 00:14, G Portokalidis wrote:
> I've been hacking Qemu for Argos, and i was wondering whether it is
> possible to execute code from a virtual peripherals memory.
Short answer is no.
The basic problem is because qemu uses dynamic translation, code is read once
in a big
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
I've been hacking Qemu for Argos, and i was wondering whether it is
possible to execute code from a virtual peripherals memory.
To be more explicit, i have coded a virtual peripheral that does
nothing, but register some physical memory for memory io. This
physical address is mapped into a process'
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
