> code (a) : for (int i = 0; i< 100; i++) c[i] = a[i] * b[i];
>
> code (b) : for (int i = 0; i< 1000; i++) for(int j = 0; j < b[i]; j++)
> c[i] += a[i];
>
> code (c) : for (int i = 0; i< 1000; i++) c[i] = HW_MUL(a[i], b[i]);
>
> I'm sure that code (b) will execute much longer that code (a) ins
En/na Paul Brook ha escrit:
> On Monday 16 April 2007 15:41, Marius Monton wrote:
>
>>> Any benchmark/performance measurements you make inside qemu are
>>> meaningless. qemu performance bears no relation whatsoever to the
>>> performance characteristics of real hardware.
>>>
>> That's t
Hi,
I just tried with cpu_disable_ticks() and cpu_enable_ticks(). It seems to
work partially: at least now system date and time are out of sync..
Maybe a more accurate way to do this is mimicking "stop" and "continue"
monitor commands:
vm_stop(EXCP_INTERRUPT);
[SystemC simulation]
vm_start()
On Monday 16 April 2007 15:41, Marius Monton wrote:
> > Any benchmark/performance measurements you make inside qemu are
> > meaningless. qemu performance bears no relation whatsoever to the
> > performance characteristics of real hardware.
>
> That's true, and I don't care about it. I'd like to get
That's true, and I don't care about it. I'd like to get a method to
stop/start time inside qemu in order to simulate execution of large
pieces of hw out of qemu (look at qemu-systemc project).
If qemu is freeze meanwhile a systemc simulation is in progress
(simulating a HW device of system), time
Hi,
For my work on QEMU-SC, I need to stop time inside qemu.
I need it in order to simulate HW modules with SystemC simulator, and
meanwhile stop qemu time.
In this way, applications running on qem should see its time freeze, and
measurements of total time spent by application + specific HW be mor
Hi,
Paul Brook wrote:
qemu is not cycle accurate or even deterministic.
Is there anything that's cycle accurate at all?
Regards
Markus
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
On Friday 29 December 2006 17:53, Màrius Montón wrote:
> Hi,
>
> As I understand, OSes running inside qemu "have" notion of time: (its
> date and time works, time(1) command works, etc.).
> My question is about how qemu manages time. I need to stop and start
> again this "virtual-time".
qemu doesn
Hi,
As I understand, OSes running inside qemu "have" notion of time: (its
date and time works, time(1) command works, etc.).
My question is about how qemu manages time. I need to stop and start
again this "virtual-time".
I just tried with cpu_disable_ticks() and cpu_enable_ticks(). It seems
to wo
On Friday 29 December 2006 16:22, Màrius Montón wrote:
> Hi,
>
> For my work on QEMU-SC, I need to stop time inside qemu.
> I need it in order to simulate HW modules with SystemC simulator, and
> meanwhile stop qemu time.
> In this way, applications running on qem should see its time freeze, and
>
Hi,
For my work on QEMU-SC, I need to stop time inside qemu.
I need it in order to simulate HW modules with SystemC simulator, and
meanwhile stop qemu time.
In this way, applications running on qem should see its time freeze, and
measurements of total time spent by application + specific HW be mor
11 matches
Mail list logo
