From: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Tim Deegan <tim@xen.org>, xen-devel@lists.xen.org
Subject: Re: [PATCH 0/4 v2] x86/hvm: RTC periodic timer adjustments
Date: Thu, 28 Mar 2013 16:36:23 -0500 [thread overview]
Message-ID: <5154B7D7.7010905@amd.com> (raw)
In-Reply-To: <51547B6202000078000C965F@nat28.tlf.novell.com>
On 3/28/2013 11:18 AM, Jan Beulich wrote:
>>>> On 28.03.13 at 17:09, Tim Deegan <tim@xen.org> wrote:
>> With these four patches, the time drift that was happening on Windows XP
>> guests goes away, at least in my testing. 3/4 is probably the most
>> important (with the other three, I still see slow drift), but the others
>> all seem like a good idea to me.
>>
>> Changes since v1:
>> - moved the irq logic patch to the end of the queue so the others
>> can be applied independently
>> - in the irq logic, keep the strobing behaviour as before
>> - store period_code instead of period and pt_active
> Acked-by: Jan Beulich <jbeulich@suse.com>
>
> Of course it would be nice if Suravee could test this in his setup,
> so we'd have another data point on the positive effects this has.
>
> Jan
I have tested this and it seems to stop drifting on my same test box
that observed the issue before.
Suravee
next prev parent reply other threads:[~2013-03-28 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 16:09 [PATCH 0/4 v2] x86/hvm: RTC periodic timer adjustments Tim Deegan
2013-03-28 16:09 ` [PATCH 1/4] x86/hvm: Run the RTC periodic timer on a consistent time series Tim Deegan
2013-03-28 16:09 ` [PATCH 2/4] x86/hvm: Avoid needlessly resetting the periodic timer Tim Deegan
2013-03-28 16:09 ` [PATCH 3/4] x86/hvm: Let the guest miss a few ticks before resetting the timer Tim Deegan
2013-03-28 16:09 ` [PATCH 4/4] x86/hvm: Centralize and simplify the RTC IRQ logic Tim Deegan
2013-03-28 16:18 ` [PATCH 0/4 v2] x86/hvm: RTC periodic timer adjustments Jan Beulich
2013-03-28 21:36 ` Suravee Suthikulanit [this message]
2013-03-28 19:57 ` Keir Fraser
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=5154B7D7.7010905@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=JBeulich@suse.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/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).