From: "Kazu" <kazoo@r3.dion.ne.jp>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] Improving timer/clock for win32
Date: Fri, 31 Mar 2006 14:49:06 +0900 [thread overview]
Message-ID: <000401c65486$d2ca4520$0464a8c0@athlon> (raw)
Hi,
This patch improves timer/clock for win32. Here is the patch and a binary.
http://www.h7.dion.ne.jp/~qemu-win/download/qemu-20060330-timer.patch
http://www.h6.dion.ne.jp/~kazuw/qemu-win/qemu-20060330-timer.zip
It supports 1ms interval interrupt.
It also improves the delay when it is used with Kqemu/Qvm86.
A main reason of delay of time is that when main_loop_wait is slept and an
interrupt timer is expired, the timer interrupt doesn't occured. I used an
event object to wake up the main loop.
I used QueryPerformanceCounter/QueryPerformanceFrequency to measure time. It
uses ACPI PM Timer on my system. Some system use RDTSC value. It depends on
your system.
It might be possible to run on SMP(HT or Multi-core) system. I haven't
tested it, though.
Regards,
Kazu
next reply other threads:[~2006-03-31 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 5:49 Kazu [this message]
2006-03-31 21:54 ` [Qemu-devel] [PATCH] Improving timer/clock for win32 André Braga
2006-04-01 1:09 ` Kazu
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='000401c65486$d2ca4520$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).