From: Tim Deegan <tim@xen.org>
To: xen-devel@lists.xen.org
Cc: suravee.suthikulpanit@amd.com, JBeulich@suse.com
Subject: [PATCH 0/4] x86/hvm: RTC periodic timer adjustments
Date: Thu, 28 Mar 2013 13:22:12 +0000 [thread overview]
Message-ID: <1364476936-15824-1-git-send-email-tim@xen.org> (raw)
With these four patches, the time drift that was happening on Windows XP
guests goes away, at least in my testing. 4/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.
1/4 is just a bit of tidying, untangling the IRQ masking logic.
2/4 is the same patch I posted before, to keep the periods aligned.
3/4 avoids calling create_periodic_time() when it's already running.
4/4 holds off disabling the timer for a few ticks, while still
disabling it if the guest is obviously ignoring the IRQ.
Cheers,
Tim.
next reply other threads:[~2013-03-28 13:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 13:22 Tim Deegan [this message]
2013-03-28 13:22 ` [PATCH 1/4] x86/hvm: Centralize and simplify the RTC IRQ logic Tim Deegan
2013-03-28 13:33 ` Andrew Cooper
2013-03-28 13:42 ` Tim Deegan
2013-03-28 13:49 ` Jan Beulich
2013-03-28 14:08 ` Tim Deegan
2013-03-28 14:22 ` Jan Beulich
2013-03-28 14:38 ` Tim Deegan
2013-03-28 15:19 ` Jan Beulich
2013-03-28 15:30 ` Tim Deegan
2013-03-28 15:41 ` Jan Beulich
2013-03-28 19:57 ` Keir Fraser
2013-03-28 13:22 ` [PATCH 2/4] x86/hvm: Run the RTC periodic timer on a consistent time series Tim Deegan
2013-03-28 13:27 ` Keir Fraser
2013-03-28 13:22 ` [PATCH 3/4] x86/hvm: Avoid needlessly resetting the periodic timer Tim Deegan
2013-03-28 13:41 ` Jan Beulich
2013-03-28 13:58 ` Tim Deegan
2013-03-28 13:22 ` [PATCH 4/4] x86/hvm: Let the guest miss a few ticks before resetting the timer Tim Deegan
2013-03-28 13:53 ` Jan Beulich
2013-03-28 14:42 ` Tim Deegan
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=1364476936-15824-1-git-send-email-tim@xen.org \
--to=tim@xen.org \
--cc=JBeulich@suse.com \
--cc=suravee.suthikulpanit@amd.com \
--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).