public inbox for kvm@vger.kernel.org
 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: [PATCH 2/5] mc146818rtc: fix clock lost after scaling coalesced irq
Date: Thu, 4 May 2017 10:51:18 +0800	[thread overview]
Message-ID: <5872c8da-35ee-fa38-802b-b865dc170c3f@gmail.com> (raw)
In-Reply-To: <46377b3a-d06e-2119-eb97-5384013b0ac8@redhat.com>



On 05/03/2017 11:15 PM, Paolo Bonzini wrote:
> 
> 
> On 12/04/2017 11:51, guangrong.xiao@gmail.com wrote:
>> +            int current_irq_coalesced = s->irq_coalesced;
>> +
>> +            s->irq_coalesced = (current_irq_coalesced * s->period) / period;
>> +
>> +            /*
>> +             * calculate the lost clock after it is scaled which should be
>> +             * compensated in the next interrupt.
>> +             */
>> +            lost_clock += current_irq_coalesced * s->period -
>> +                            s->irq_coalesced * period;
> 
> This is:
> 
>     lost_clock = current_irq_coalesced * s->period -
> 	(current_irq_coalesced * s->period) / period * period;
> 
> i.e.
> 
>     /* When switching from a shorter to a longer period, scale down the
>      * missing ticks since we expect the OS handler to treat the delayed
>      * ticks as longer.  Any leftovers are put back into next_irq_clock.
>      *
>      * When switching to a shorter period, scale up the missing ticks
>      * since we expect the OS handler to treat the delayed ticks as
>      * shorter.
>      */
>     lost_clock = (s->irq_coalesced * s->period) % period;
>     s->irq_coalesced = (s->irq_coalesced * s->period) / period;
> 
> Is this correct?
> 

Yes, it is correct, it looks smarter, will apply it in the next version.

Thanks!

  reply	other threads:[~2017-05-04  2:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12  9:51 [PATCH 0/5] mc146818rtc: fix Windows VM clock faster guangrong.xiao
2017-04-12  9:51 ` [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 ` [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 [this message]
2017-04-12  9:51 ` [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 ` [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 ` [PATCH 5/5] mc146818rtc: embrace all x86 specific code guangrong.xiao
2017-04-13  6:37 ` [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       ` 答复: " 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       ` Paolo Bonzini
2017-04-14  6:07         ` [Qemu-devel] " 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=5872c8da-35ee-fa38-802b-b865dc170c3f@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