From: Dor Laor <dlaor@redhat.com>
To: Glauber Costa <glommer@gmail.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
Glauber Costa <glommer@redhat.com>,
aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] re-set rtc date on reset handler
Date: Tue, 08 Sep 2009 17:55:28 +0300 [thread overview]
Message-ID: <4AA67060.8030804@redhat.com> (raw)
In-Reply-To: <5d6222a80909011600l264f1f3cpb0b8d503dac9a26a@mail.gmail.com>
On 09/02/2009 02:00 AM, Glauber Costa wrote:
> On Tue, Sep 1, 2009 at 1:56 PM, Blue Swirl<blauwirbel@gmail.com> wrote:
>> On Tue, Sep 1, 2009 at 7:22 PM, Glauber Costa<glommer@redhat.com> wrote:
>>> guests without a stable timesource such as kvm-clock will grab the wallclock
>>> from our rtc chip. However, we only sync the date when we first launch qemu.
>>> If a guest goes through a series of reboot cycles, it will slowly see time
>>> getting far behind the host.
>>>
>>> The proposal of this patch is to set the date to host clock again in the reset
>>> handler. With this patch, I see a Fedora guest keeping its clock in sync upon
>>> an ulimited number of reboots.
>>
>> A different approach is used in m48t59.c: the guest clock is generated
>> directly from host clock without any timers and only a fixed offset
> You mean at every ioport read? I actually thought about that, but was
> too lazy...
>
>
You also need to handle the -startdate flag of qemu.
In this case you need to keep the offset and not read the host time.
next prev parent reply other threads:[~2009-09-08 14:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 16:22 [Qemu-devel] [PATCH] re-set rtc date on reset handler Glauber Costa
2009-09-01 16:56 ` Blue Swirl
2009-09-01 23:00 ` Glauber Costa
2009-09-08 14:55 ` Dor Laor [this message]
2009-09-08 16:15 ` [Qemu-devel] " Jan Kiszka
2009-09-08 16:50 ` Jan Kiszka
2009-09-08 17:00 ` Jan Kiszka
2009-09-09 12:28 ` Dor Laor
2009-09-09 12:57 ` Jan Kiszka
2009-09-09 13:27 ` Avi Kivity
2009-09-09 13:31 ` Jan Kiszka
2009-09-09 15:04 ` Avi Kivity
2009-09-09 15:34 ` Anthony Liguori
2009-09-09 16:09 ` Gleb Natapov
2009-09-09 17:52 ` Anthony Liguori
2009-09-09 18:40 ` Gleb Natapov
2009-09-09 18:50 ` Anthony Liguori
2009-09-09 18:25 ` Avi Kivity
2009-09-09 18:33 ` Anthony Liguori
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=4AA67060.8030804@redhat.com \
--to=dlaor@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=glommer@gmail.com \
--cc=glommer@redhat.com \
--cc=qemu-devel@nongnu.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 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.