From: "Kazu" <kazoo@r3.dion.ne.jp>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Workaround for windbg
Date: Thu, 3 Aug 2006 12:19:38 +0900 [thread overview]
Message-ID: <000401c6b6ab$a7042f50$0464a8c0@athlon> (raw)
Hi,
My previous patch is not enough to use windbg. A rate of loop in main_loop
in vl.c drops a lot.
The rate does not drop for Fedora Core 4 guest but not good for RedHat 7.2
and Windows 2000. It is expected at least 1000 cycles/sec, but the rate
drops to 130 cycles/sec while CPU load is high. It is the case while OS is
booting. The rate is slow so that a communication through serial line is
slow.
I made a workaround for it and checked the data sending/receiving rate by
it. The patch exits CPU loop in cpu_exec every 100 times and handle I/O of
serial data. The rate of loop in main_loop is about 30000 cycles/sec. Win2k
booting time with windbg is much improved.
The patch is not efficient so it can only be used for windbg. It seems that
cpu_interrupt does not work while CPU load is high depending on a guest OS.
Binary.
http://www.h6.dion.ne.jp/~kazuw/qemu-win/qemu-0.8.2-windbg.zip
Patch.
http://www.h7.dion.ne.jp/~qemu-win/download/qemu-20060730-windbg.patch
Regards,
Kazu
reply other threads:[~2006-08-03 3:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000401c6b6ab$a7042f50$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 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).