|
From: | Marius Monton |
Subject: | Re: [Qemu-devel] time inside qemu |
Date: | Mon, 16 Apr 2007 16:41:28 +0200 |
User-agent: | Mozilla Thunderbird 1.5.0.10 (X11/20070403) |
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 should be freeze also. In this way, execution time of a program inside qemu should appear shorter when using accelerator HW than only SW application. I know these times are not reals, but it should be enough to estimate correctness and execution time on real platforms. Does a way to stop/start time inside qemu? Thanks, Màrius En/na Paul Brook ha escrit: 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't maintain virtual time, it just uses the real host time.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..I suspect you'll find that for anything other than very coarse user (ie. user stop/continue) these are effectively useless. Any benchmark/performance measurements you make inside qemu are meaningless. qemu performance bears no relation whatsoever to the performance characteristics of real hardware. Paul _______________________________________________ Qemu-devel mailing list address@hidden http://lists.nongnu.org/mailman/listinfo/qemu-devel --
|
marius.monton.vcf
Description: Vcard
[Prev in Thread] | Current Thread | [Next in Thread] |