From: guangrong.xiao@gmail.com
To: pbonzini@redhat.com, mst@redhat.com, mtosatti@redhat.com
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
yunfangtai@tencent.com,
Xiao Guangrong <xiaoguangrong@tencent.com>
Subject: [Qemu-devel] [PATCH v2 0/5] mc146818rtc: fix Windows VM clock faster
Date: Thu, 4 May 2017 19:59:43 +0800 [thread overview]
Message-ID: <20170504115948.3048-1-xiaoguangrong@tencent.com> (raw)
From: Xiao Guangrong <xiaoguangrong@tencent.com>
Changelog in v2:
Thanks to Paolo's review, the changes in this version are:
1) merge patch 2, 3, 4 together
2) use a nice way ((value ^ new_value) & BIT_MASK) to check if updating
for periodic timer is needed
3) use a smarter way to calculate coalesced irqs and lost_clock
4) make sure only x86 can enable LOST_TICK_POLICY_SLEW
5) make the code depends on LOST_TICK_POLICY_SLEW rather than
TARGET_I386
We noticed that the clock on some windows VMs, e.g, Window7 and window8
is really faster and the issue can be easily reproduced by staring the
VM with '-rtc base=localtime,clock=vm,driftfix=slew -no-hpet' and
running attached code in the guest
The root cause is that the clock will be lost if the periodic period is
changed as currently code counts the next periodic time like this:
next_irq_clock = (cur_clock & ~(period - 1)) + period;
consider the case if cur_clock = 0x11FF and period = 0x100, then the
next_irq_clock is 0x1200, however, there is only 1 clock left to trigger
the next irq. Unfortunately, Windows guests (at least Windows7) change
the period very frequently if it runs the attached code, so that the
lost clock is accumulated, the wall-time become faster and faster
The main idea to fix the issue is we use a accurate clock period to
calculate the next irq:
next_irq_clock = cur_clock + period;
After that, it is really convenient to compensate clock if it is needed
The code running in windows VM is attached:
// TimeInternalTest.cpp : Defines the entry point for the console application.
//
#include "stdafx.h"
#pragma comment(lib, "winmm")
#include <stdio.h>
#include <windows.h>
#define SWITCH_PEROID 13
int _tmain(int argc, _TCHAR* argv[])
{
if (argc != 2)
{
printf("parameter error!\n");
printf("USAGE: *.exe time(ms)\n");
printf("example: *.exe 40\n");
return 0;
}
else
{
DWORD internal = atoi((char *)argv[1]);
DWORD count = 0;
while (1)
{
count++;
timeBeginPeriod(1);
DWORD start = timeGetTime();
Sleep(internal);
timeEndPeriod(1);
if ((count % SWITCH_PEROID) == 0) {
Sleep(1);
}
}
}
return 0;
}
Tai Yunfang (1):
mc146818rtc: precisely count the clock for periodic timer
Xiao Guangrong (4):
mc146818rtc: update periodic timer only if it is needed
mc146818rtc: ensure LOST_TICK_POLICY_SLEW is only enabled on
TARGET_I386
mc146818rtc: drop unnecessary '#ifdef TARGET_I386'
mc146818rtc: embrace all x86 specific code
hw/timer/mc146818rtc.c | 204 ++++++++++++++++++++++++++++++++++---------------
1 file changed, 144 insertions(+), 60 deletions(-)
--
2.9.3
next reply other threads:[~2017-05-04 12:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 11:59 guangrong.xiao [this message]
2017-05-04 11:59 ` [Qemu-devel] [PATCH v2 1/5] mc146818rtc: update periodic timer only if it is needed guangrong.xiao
2017-05-04 11:59 ` [Qemu-devel] [PATCH v2 2/5] mc146818rtc: precisely count the clock for periodic timer guangrong.xiao
2017-05-04 12:31 ` Paolo Bonzini
2017-05-05 6:29 ` Xiao Guangrong
2017-05-04 11:59 ` [Qemu-devel] [PATCH v2 3/5] mc146818rtc: ensure LOST_TICK_POLICY_SLEW is only enabled on TARGET_I386 guangrong.xiao
2017-05-04 11:59 ` [Qemu-devel] [PATCH v2 4/5] mc146818rtc: drop unnecessary '#ifdef TARGET_I386' guangrong.xiao
2017-05-04 11:59 ` [Qemu-devel] [PATCH v2 5/5] mc146818rtc: embrace all x86 specific code guangrong.xiao
2017-05-04 14:00 ` [Qemu-devel] [PATCH v2 0/5] mc146818rtc: fix Windows VM clock faster no-reply
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=20170504115948.3048-1-xiaoguangrong@tencent.com \
--to=guangrong.xiao@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiaoguangrong@tencent.com \
--cc=yunfangtai@tencent.com \
/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).