All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kazu" <kazoo@r3.dion.ne.jp>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] objective benchmark?
Date: Tue, 16 May 2006 15:41:45 +0900	[thread overview]
Message-ID: <000e01c678b3$cd372460$0464a8c0@athlon> (raw)
In-Reply-To: 44695113.8040708@us.ibm.com

Anthony Liguori wrote:

> Mikhail Ramendik wrote:
>> Hello,
>>
>> As I have reported before, it seems that on my host linux system kqemu
does
>> not work with guest win98se.
>>
>> Is there any benchmark that I could run in the guest, with and without
kqemu,
>> to check if this is so objectively? (Ideally I'd like two benchmarks -
16-bit
>> and 32-bit code).
>>
>
> The vast majority of guest benchmarking programs are going to give you
> invalid results.  The clock within QEMU (rdtsc and wall clock) are not
> very reliable and this is going to skew the results.
>

If you set /proc/sys/dev/rtc/max-user-freq to 1024 and disable cpuspeed
service that is related to SpeedStep/PowerNow! on a host OS, the clock in
guest OS works fine.

I checked it on i686/x86_64 Linux host.

Regards,
Kazu

  reply	other threads:[~2006-05-16  6:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-15 18:03 [Qemu-devel] objective benchmark? Mikhail Ramendik
2006-05-15 20:25 ` Natalia Portillo
2006-05-15 21:13   ` Mikhail Ramendik
2006-05-16  0:07 ` NyOS
2006-05-16  4:12 ` Anthony Liguori
2006-05-16  6:41   ` Kazu [this message]
2006-05-16  6:55     ` Christian MICHON
2006-05-16  9:26       ` Kazu
2006-05-16 10:23         ` Christian MICHON
2006-05-17  7:24           ` Kazu
2006-05-16 11:48     ` Lonnie Mendez
2006-05-17  7:24       ` Kazu
2006-05-17  9:09         ` Lonnie Mendez
2006-05-17 19:18         ` Fabrice Bellard
  -- strict thread matches above, loose matches on Subject: below --
2006-05-16 12:53 Ben Taylor

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='000e01c678b3$cd372460$0464a8c0@athlon' \
    --to=kazoo@r3.dion.ne.jp \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.