qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Markus Schiltknecht <markus@bluegap.ch>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] relative time
Date: Sat, 09 Sep 2006 20:36:51 +0200	[thread overview]
Message-ID: <450309C3.9070403@bluegap.ch> (raw)

Hello qemu developers,

I've been unable to find information about date and time in qemu. Two 
questions the simpler one:

Can I set the date and time of the system clock at start of the 
emulation (or in the manager console)? I've seen a patch [1], but that 
doesn't seem to be included in my build (from debian sid):

Now the more complex one: I would like to do 'relative benchmarks', i.e. 
comparing one product to another. I don't mind very much how fast my 
machines are, but I want them to be equally fast, even if I use two, 
three or ten of those on my machine.

Therefore I would like to limit CPU time. Say limiting it to virtually 1 
MHz. Optionally one could even take into account processor caches...

As some of the benchmarks I would like to run are harddrive dependant, 
could one limit their speed? Try simulating harddisk head positions and 
rotation?

Limiting the network speed can be done quite accurately with Linux on 
tap devices I don't know about latency, though.

All in all: I would like to simulate a system which is exactly (or quite 
close to) a 100 times slower than a given real one.

Has anybody tried (or requested) something like that already? How 
difficult would it be to teach qemu to 'slow down'? How accurate could 
such a slow down be?

Regards

Markus

[1]: http://lists.gnu.org/archive/html/qemu-devel/2006-01/msg00128.html

             reply	other threads:[~2006-09-09 18:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-09 18:36 Markus Schiltknecht [this message]
2006-09-09 18:40 ` [Qemu-devel] relative time Paul Brook

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=450309C3.9070403@bluegap.ch \
    --to=markus@bluegap.ch \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).