From: Paolo Bonzini <pbonzini@redhat.com>
To: Xiao Guangrong <guangrong.xiao@gmail.com>,
Hailiang Zhang <zhang.zhanghailiang@huawei.com>,
Xiao Guangrong <xiaoguangrong.eric@gmail.com>,
"mst@redhat.com" <mst@redhat.com>,
"mtosatti@redhat.com" <mtosatti@redhat.com>
Cc: xuquan8@huawei.com,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"yunfangtai@tencent.com" <yunfangtai@tencent.com>,
Xiao Guangrong <xiaoguangrong@tencent.com>
Subject: Re: 答复: [PATCH 0/5] mc146818rtc: fix Windows VM clock faster
Date: Wed, 19 Apr 2017 18:44:50 +0200 [thread overview]
Message-ID: <a42dcfc6-a2c0-407a-4246-cd9da095220c@redhat.com> (raw)
In-Reply-To: <49848876-f710-8395-3029-47b8e71dc29f@gmail.com>
On 19/04/2017 13:13, Xiao Guangrong wrote:
>
>
> On 04/19/2017 06:41 PM, Hailiang Zhang wrote:
>
>>> Hi Hailiang,
>>>
>>> Does this patchset work for you? :)
>>
>> Yes, i think it works for us, nice work :)
>
> Appreciate your test, Hailiang!
>
> Paolo, any comment? :)
Will review as soon as 2.9 gets out. :)
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Xiao Guangrong <guangrong.xiao@gmail.com>,
Hailiang Zhang <zhang.zhanghailiang@huawei.com>,
Xiao Guangrong <xiaoguangrong.eric@gmail.com>,
"mst@redhat.com" <mst@redhat.com>,
"mtosatti@redhat.com" <mtosatti@redhat.com>
Cc: xuquan8@huawei.com,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"yunfangtai@tencent.com" <yunfangtai@tencent.com>,
Xiao Guangrong <xiaoguangrong@tencent.com>
Subject: Re: [Qemu-devel] 答复: [PATCH 0/5] mc146818rtc: fix Windows VM clock faster
Date: Wed, 19 Apr 2017 18:44:50 +0200 [thread overview]
Message-ID: <a42dcfc6-a2c0-407a-4246-cd9da095220c@redhat.com> (raw)
In-Reply-To: <49848876-f710-8395-3029-47b8e71dc29f@gmail.com>
On 19/04/2017 13:13, Xiao Guangrong wrote:
>
>
> On 04/19/2017 06:41 PM, Hailiang Zhang wrote:
>
>>> Hi Hailiang,
>>>
>>> Does this patchset work for you? :)
>>
>> Yes, i think it works for us, nice work :)
>
> Appreciate your test, Hailiang!
>
> Paolo, any comment? :)
Will review as soon as 2.9 gets out. :)
Paolo
next prev parent reply other threads:[~2017-04-19 16:44 UTC|newest]
Thread overview: 59+ 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 ` [Qemu-devel] " guangrong.xiao
2017-04-12 9:51 ` [PATCH 1/5] mc146818rtc: update periodic timer only if it is needed guangrong.xiao
2017-04-12 9:51 ` [Qemu-devel] " guangrong.xiao
2017-05-03 15:42 ` Paolo Bonzini
2017-05-03 15:42 ` [Qemu-devel] " Paolo Bonzini
2017-05-04 3:27 ` Xiao Guangrong
2017-05-04 3:27 ` [Qemu-devel] " Xiao Guangrong
2017-04-12 9:51 ` [PATCH 2/5] mc146818rtc: fix clock lost after scaling coalesced irq guangrong.xiao
2017-04-12 9:51 ` [Qemu-devel] " guangrong.xiao
2017-05-03 15:15 ` Paolo Bonzini
2017-05-03 15:15 ` [Qemu-devel] " Paolo Bonzini
2017-05-04 2:51 ` Xiao Guangrong
2017-05-04 2:51 ` [Qemu-devel] " Xiao Guangrong
2017-04-12 9:51 ` [PATCH 3/5] mc146818rtc: properly count the time for the next interrupt guangrong.xiao
2017-04-12 9:51 ` [Qemu-devel] " guangrong.xiao
2017-05-03 15:32 ` Paolo Bonzini
2017-05-03 15:32 ` [Qemu-devel] " Paolo Bonzini
2017-05-04 2:54 ` Xiao Guangrong
2017-05-04 2:54 ` [Qemu-devel] " Xiao Guangrong
2017-05-04 12:02 ` Paolo Bonzini
2017-05-04 12:02 ` [Qemu-devel] " Paolo Bonzini
2017-04-12 9:51 ` [PATCH 4/5] mc146818rtc: move x86 specific code out of periodic_timer_update guangrong.xiao
2017-04-12 9:51 ` [Qemu-devel] " guangrong.xiao
2017-05-03 15:39 ` Paolo Bonzini
2017-05-03 15:39 ` [Qemu-devel] " Paolo Bonzini
2017-05-04 3:25 ` Xiao Guangrong
2017-05-04 3:25 ` [Qemu-devel] " Xiao Guangrong
2017-05-04 7:08 ` Paolo Bonzini
2017-05-04 7:08 ` [Qemu-devel] " Paolo Bonzini
2017-04-12 9:51 ` [PATCH 5/5] mc146818rtc: embrace all x86 specific code guangrong.xiao
2017-04-12 9:51 ` [Qemu-devel] " guangrong.xiao
2017-04-13 6:37 ` [PATCH 0/5] mc146818rtc: fix Windows VM clock faster Paolo Bonzini
2017-04-13 6:37 ` [Qemu-devel] " Paolo Bonzini
2017-04-13 8:39 ` Xiao Guangrong
2017-04-13 8:39 ` [Qemu-devel] " Xiao Guangrong
2017-04-13 8:52 ` Xiao Guangrong
2017-04-13 8:52 ` [Qemu-devel] " Xiao Guangrong
2017-04-13 9:05 ` 答复: " Zhanghailiang
2017-04-13 9:05 ` [Qemu-devel] " Zhanghailiang
2017-04-13 9:18 ` Xiao Guangrong
2017-04-13 9:18 ` [Qemu-devel] " Xiao Guangrong
2017-04-13 9:29 ` Hailiang Zhang
2017-04-13 9:29 ` [Qemu-devel] " Hailiang Zhang
2017-04-13 9:35 ` Xiao Guangrong
2017-04-13 9:35 ` [Qemu-devel] " Xiao Guangrong
2017-04-13 9:38 ` Hailiang Zhang
2017-04-13 9:38 ` [Qemu-devel] " Hailiang Zhang
2017-04-19 2:02 ` Xiao Guangrong
2017-04-19 2:02 ` [Qemu-devel] " Xiao Guangrong
2017-04-19 10:41 ` Hailiang Zhang
2017-04-19 10:41 ` [Qemu-devel] " Hailiang Zhang
2017-04-19 11:13 ` Xiao Guangrong
2017-04-19 11:13 ` [Qemu-devel] " Xiao Guangrong
2017-04-19 16:44 ` Paolo Bonzini [this message]
2017-04-19 16:44 ` Paolo Bonzini
2017-04-14 5:09 ` 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=a42dcfc6-a2c0-407a-4246-cd9da095220c@redhat.com \
--to=pbonzini@redhat.com \
--cc=guangrong.xiao@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiaoguangrong.eric@gmail.com \
--cc=xiaoguangrong@tencent.com \
--cc=xuquan8@huawei.com \
--cc=yunfangtai@tencent.com \
--cc=zhang.zhanghailiang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.