qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Xiao Guangrong <guangrong.xiao@gmail.com>
To: Paolo Bonzini <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: Re: [Qemu-devel] [PATCH v3 0/5] mc146818rtc: fix Windows VM clock faster
Date: Thu, 18 May 2017 10:26:54 +0800	[thread overview]
Message-ID: <0900def5-6049-4338-1eb0-8a0404c6c839@gmail.com> (raw)
In-Reply-To: <9626326d-977f-bf26-851a-59d420f27993@redhat.com>



On 05/10/2017 05:53 PM, Paolo Bonzini wrote:
> 
> 
> On 10/05/2017 10:32, guangrong.xiao@gmail.com wrote:
>> From: Xiao Guangrong <xiaoguangrong@tencent.com>
>>
>> Changelog in v3:
>> Thanks to Paolo's the elaborate review comments, this version
>> simplifies the logic of periodic_timer_update() significantly
>> that includes:
>> 1) introduce rtc_periodic_clock_ticks() that takes both regA and
>>     regB into account and returns the period clock
>> 2) count the clocks since last interrupt by always using current
>>     clock subtracts the clock when last interrupt happened
>> 3) improve the assert() logic
>>
>> Paolo, all you comments have been reflected in this version except
>> globally using s->period because in the current code, only x86 is
>> using s->period so that we should obey this rule to keep compatible
>> migration. I have added the comment to explain this suitable in the
>> code:
>>
>>              /*
>>               * as the old QEMUs only used s->period for the case that
>>               * LOST_TICK_POLICY_SLEW is used, in order to keep the
>>               * compatible migration, we obey the rule as old QEMUs.
>>               */
>>              s->period = period;
>> If anything i missed, please let me know. :)
> 
> Looks great.  Thanks for following up quickly on the reviews.
> 

Paolo, if it is okay to you, could you please consider to merge this
patchset? ;)

  reply	other threads:[~2017-05-18  2:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10  8:32 [Qemu-devel] [PATCH v3 0/5] mc146818rtc: fix Windows VM clock faster guangrong.xiao
2017-05-10  8:32 ` [Qemu-devel] [PATCH v3 1/5] mc146818rtc: update periodic timer only if it is needed guangrong.xiao
2017-05-10  8:32 ` [Qemu-devel] [PATCH v3 2/5] mc146818rtc: precisely count the clock for periodic timer guangrong.xiao
2017-05-10  8:32 ` [Qemu-devel] [PATCH v3 3/5] mc146818rtc: ensure LOST_TICK_POLICY_SLEW is only enabled on TARGET_I386 guangrong.xiao
2017-05-13 22:13   ` Philippe Mathieu-Daudé
2017-05-10  8:32 ` [Qemu-devel] [PATCH v3 4/5] mc146818rtc: drop unnecessary '#ifdef TARGET_I386' guangrong.xiao
2017-05-13 22:12   ` Philippe Mathieu-Daudé
2017-05-10  8:32 ` [Qemu-devel] [PATCH v3 5/5] mc146818rtc: embrace all x86 specific code guangrong.xiao
2017-05-10  9:53 ` [Qemu-devel] [PATCH v3 0/5] mc146818rtc: fix Windows VM clock faster Paolo Bonzini
2017-05-18  2:26   ` Xiao Guangrong [this message]
2017-05-18  7:52     ` Paolo Bonzini
2017-05-18 13:38       ` Xiao Guangrong
2017-05-18 13:51         ` Paolo Bonzini
2017-05-10 10:04 ` 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=0900def5-6049-4338-1eb0-8a0404c6c839@gmail.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).