From: "Kazu" <kazoo@r3.dion.ne.jp>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] objective benchmark?
Date: Wed, 17 May 2006 16:24:58 +0900 [thread overview]
Message-ID: <005601c67983$00ea7580$0464a8c0@athlon> (raw)
In-Reply-To: 46d6db660605160323g2316e3e7qec55e0263faf723c@mail.gmail.com
Tuesday, May 16, 2006 7:23 PM Christian MICHON wrote:
>On 5/16/06, Kazu <kazoo@r3.dion.ne.jp> wrote:
>> It is normal that 2.4 kernel boots faster than 2.6 kernel, isn't it? I
don't
>> know why Solaris x86 10 doesn't work.
>solaris works, it's just painfully slow.
>lots of time is wasted in ide-probing inside 2.6.x, because of the
>way time is measured in the qemu guest.
>Maybe recompiling 2.6.x guest kernel, telling it which internal timer to
>use would be better. Does anyone know how to do this or tried it already?
Fedora Core 3 doesn't boot in 0.8.0 binary. But it boots almost the same
speed in 0.8.1 binary as on Linux host.
I measured FC3 booting time without kqemu.
On WinXP host:
0.8.0 binary can't boot.
0.8.1 binary 4min 15sec
On Linux host:
0.8.0 4min 15sec
0.8.1 4min 5sec
I measured Knoppix v3.8 booting time.
On WinXP host: fb800x600 desktop=icewm
0.8.0 5min 54sec
0.8.1 3min 4sec
>From Knoppix booting, I think time for scanning hardware is improved as on
Linux host.
I think the problem is not related to measuring time.
Regards,
Kazu
next prev parent reply other threads:[~2006-05-17 7:24 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
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 [this message]
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='005601c67983$00ea7580$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.