From: Avi Kivity <avi@qumranet.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Dan Kenigsberg <danken@qumranet.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Patch] [kinda-resend] persistent real-time-clock
Date: Tue, 06 May 2008 00:13:58 +0300 [thread overview]
Message-ID: <481F7896.1000409@qumranet.com> (raw)
In-Reply-To: <481F6CAF.6060308@codemonkey.ws>
Anthony Liguori wrote:
>>
>> I'm not sure I understood what you suggest here.
>>
>> Plainly storing the rtc state on file is not enough, as unlike with real
>> hardware, nothing will advance it when the power is off.
>>
>
> If you made the CMOS non-volatile, what you would store in the CMOS is
> the clock-offset, not the actual clock time. Then when the VM started
> up again, it would Just Work.
>
> You would probably have to use a different location in CMOS to store
> the offset than what the guest relies on to read the current time.
Under this, the CMOS would not be read by the guest at any time. So why
store the CMOS at all? Store the offset somewhere and avoid the CMOS
(gaining the ability to work on targets without nonvolatile memory).
It's config file territory, not CMOS.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2008-05-05 21:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 15:45 [Qemu-devel] [Patch] [kinda-resend] persistent real-time-clock Dan Kenigsberg
2008-04-27 16:39 ` Avi Kivity
2008-04-28 6:54 ` Dan Kenigsberg
2008-04-28 7:11 ` Avi Kivity
2008-04-30 12:22 ` Sergey Bychkov
2008-04-27 16:58 ` Anthony Liguori
2008-04-28 8:00 ` Dan Kenigsberg
2008-05-01 8:48 ` Dan Kenigsberg
2008-05-05 20:23 ` Anthony Liguori
2008-05-05 21:13 ` Avi Kivity [this message]
2008-05-05 22:38 ` Anthony Liguori
2008-05-06 8:26 ` Tristan Gingold
2008-05-06 8:53 ` Laurent Vivier
2008-04-27 21:28 ` Jamie Lokier
2008-04-28 7:27 ` Dan Kenigsberg
2008-04-30 12:21 ` Sergey Bychkov
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=481F7896.1000409@qumranet.com \
--to=avi@qumranet.com \
--cc=anthony@codemonkey.ws \
--cc=danken@qumranet.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 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).