qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 0/5] mc146818rtc: fix Windows VM clock faster
Date: Wed, 12 Apr 2017 17:51:06 +0800	[thread overview]
Message-ID: <20170412095111.11728-1-xiaoguangrong@tencent.com> (raw)

From: Xiao Guangrong <xiaoguangrong@tencent.com>

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: properly count the time for the next interrupt

Xiao Guangrong (4):
  mc146818rtc: update periodic timer only if it is needed
  mc146818rtc: fix clock lost after scaling coalesced irq
  mc146818rtc: move x86 specific code out of periodic_timer_update
  mc146818rtc: embrace all x86 specific code

 hw/timer/mc146818rtc.c | 370 ++++++++++++++++++++++++++++++++++++-------------
 1 file changed, 272 insertions(+), 98 deletions(-)

-- 
2.9.3

             reply	other threads:[~2017-04-12  9:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12  9:51 guangrong.xiao [this message]
2017-04-12  9:51 ` [Qemu-devel] [PATCH 1/5] mc146818rtc: update periodic timer only if it is needed guangrong.xiao
2017-05-03 15:42   ` Paolo Bonzini
2017-05-04  3:27     ` Xiao Guangrong
2017-04-12  9:51 ` [Qemu-devel] [PATCH 2/5] mc146818rtc: fix clock lost after scaling coalesced irq guangrong.xiao
2017-05-03 15:15   ` Paolo Bonzini
2017-05-04  2:51     ` Xiao Guangrong
2017-04-12  9:51 ` [Qemu-devel] [PATCH 3/5] mc146818rtc: properly count the time for the next interrupt guangrong.xiao
2017-05-03 15:32   ` Paolo Bonzini
2017-05-04  2:54     ` Xiao Guangrong
2017-05-04 12:02       ` Paolo Bonzini
2017-04-12  9:51 ` [Qemu-devel] [PATCH 4/5] mc146818rtc: move x86 specific code out of periodic_timer_update guangrong.xiao
2017-05-03 15:39   ` Paolo Bonzini
2017-05-04  3:25     ` Xiao Guangrong
2017-05-04  7:08       ` Paolo Bonzini
2017-04-12  9:51 ` [Qemu-devel] [PATCH 5/5] mc146818rtc: embrace all x86 specific code guangrong.xiao
2017-04-13  6:37 ` [Qemu-devel] [PATCH 0/5] mc146818rtc: fix Windows VM clock faster Paolo Bonzini
2017-04-13  8:39   ` Xiao Guangrong
2017-04-13  8:52     ` Xiao Guangrong
2017-04-13  9:05       ` [Qemu-devel] 答复: " Zhanghailiang
2017-04-13  9:18         ` Xiao Guangrong
2017-04-13  9:29           ` Hailiang Zhang
2017-04-13  9:35             ` Xiao Guangrong
2017-04-13  9:38               ` Hailiang Zhang
2017-04-19  2:02                 ` Xiao Guangrong
2017-04-19 10:41                   ` Hailiang Zhang
2017-04-19 11:13                     ` Xiao Guangrong
2017-04-19 16:44                       ` Paolo Bonzini
2017-04-14  5:09       ` [Qemu-devel] " Paolo Bonzini
2017-04-14  6:07         ` Xiao Guangrong

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=20170412095111.11728-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).