qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Zachary Amsden <zamsden@redhat.com>,
	qemu-devel@nongnu.org, Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/3] Let RTC follow backward jumps of host clock immediately
Date: Sat, 23 Jul 2011 11:52:41 -0500	[thread overview]
Message-ID: <4E2AFC59.2070109@us.ibm.com> (raw)
In-Reply-To: <cover.1308571574.git.jan.kiszka@siemens.com>

On 06/20/2011 07:06 AM, Jan Kiszka wrote:
> Just noticed that this issue is still unfixed because my series was
> somehow forgotten. So I've rebased it over current master, refactored it
> to use the generic Notifier infrastructure and renamed it to "clock
> reset notifier" to avoid confusion with icount related "warping". Please
> review / apply before 0.15-rc0, it fixes a relevant issue.
>
> Original series description:
>
> By default, we base the mc146818 RTC on the host clock (CLOCK_REALTIME).
> This works fine if only the frequency of the host clock is tuned (e.g.
> by NTP) or if it is set to a future time. However, if the host is tuned
> backward, e.g. because NTP obtained the correct time after the guest was
> already started or the admin decided to tune the local time, we see an
> unpleasant effect in the guest: The RTC will stall for the period the
> host clock is set back. We identified that one prominent guest affected
> by this is Windows which relies on the periodic RTC interrupt for time
> keeping.
>
> This series address the issue by detecting those warps and providing a
> callback mechanism to device models. The RTC is enabled to update its
> timers and register content immediately. Tested successfully both with
> hwclock in a Linux guest and by monitoring the Windows clock while
> fiddling with the host time.
>
> Note that if this kind of RTC adjustment is not wanted, the user is
> still free to decouple the RTC from the host clock and base it on the
> VM clock - just like before.
>
> Jan Kiszka (3):
>    notifier: Pass data argument to callback
>    qemu-timer: Introduce clock reset notifier
>    mc146818rtc: Handle host clock resets

Applied.  Thanks.

Regards,

Anthony Liguori

>
>   hw/fw_cfg.c      |    2 +-
>   hw/mc146818rtc.c |   20 ++++++++++++++++++++
>   input.c          |    2 +-
>   migration.c      |   12 ++++++------
>   notify.c         |    4 ++--
>   notify.h         |    4 ++--
>   qemu-timer.c     |   29 ++++++++++++++++++++++++++++-
>   qemu-timer.h     |    5 +++++
>   ui/sdl.c         |    2 +-
>   ui/spice-core.c  |    2 +-
>   ui/spice-input.c |    4 ++--
>   ui/vnc.c         |    4 ++--
>   usb-linux.c      |    2 +-
>   vl.c             |    4 ++--
>   xen-all.c        |    2 +-
>   15 files changed, 75 insertions(+), 23 deletions(-)
>
>
>

      parent reply	other threads:[~2011-07-23 16:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20 12:06 [Qemu-devel] [PATCH v2 0/3] Let RTC follow backward jumps of host clock immediately Jan Kiszka
2011-06-20 12:06 ` [Qemu-devel] [PATCH v2 1/3] notifier: Pass data argument to callback Jan Kiszka
2011-06-20 12:06 ` [Qemu-devel] [PATCH v2 2/3] qemu-timer: Introduce clock reset notifier Jan Kiszka
2011-06-20 12:06 ` [Qemu-devel] [PATCH v2 3/3] mc146818rtc: Handle host clock resets Jan Kiszka
2011-07-23 16:52 ` Anthony Liguori [this message]

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=4E2AFC59.2070109@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=gleb@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zamsden@redhat.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).