From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Blue Swirl <blauwirbel@gmail.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Dor Laor <dlaor@redhat.com>, Glauber Costa <glommer@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 0/5] Refactor and enhance RTC configuration
Date: Wed, 09 Sep 2009 15:18:54 -0500 [thread overview]
Message-ID: <4AA80DAE.8030006@codemonkey.ws> (raw)
In-Reply-To: <4AA80970.90000@web.de>
Jan Kiszka wrote:
> Anthony Liguori wrote:
>
>> No, it isn't. To introduce -rtc properly, you should use QemuOpts. We
>> shouldn't be introducing new options that don't conform to QemuOpts
>> syntax and the best way to do that is to just use QemuOpts.
>>
>
> Yes, QemuOpts is a must-have for -rtc. So you agree to introduce -rtc
> (in addition to the qdev-based configuration, of course)?
>
Yup.
>> Hard to say. Doesn't the rtc keep track of wallclock time even on power
>> off? I think using host_clock unconditionally does actually make sense.
>>
>>
>
> Moreover, quite a few (of not all?) other RTCs use the host time
> already. Well, I would be happy to avoid that 'clock' knob. So if there
> are no concerns, I will unconditionally switch MC146818 to host_clock.
>
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-09-09 20:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 15:11 [Qemu-devel] [PATCH 0/5] Refactor and enhance RTC configuration Jan Kiszka
2009-09-09 15:11 ` [Qemu-devel] [PATCH 3/5] Introduce QEMU_CLOCK_HOST Jan Kiszka
2009-09-09 15:11 ` [Qemu-devel] [PATCH 4/5] Refactor RTC command line switches Jan Kiszka
2009-09-09 15:11 ` [Qemu-devel] [PATCH 2/5] win32: Drop dead dyntick timer code Jan Kiszka
2009-09-09 15:11 ` [Qemu-devel] [PATCH 5/5] Enable host-clock-based RTC Jan Kiszka
2009-09-09 15:11 ` [Qemu-devel] [PATCH 1/5] Rename QEMU_TIMER_* to QEMU_CLOCK_* Jan Kiszka
2009-09-09 15:40 ` [Qemu-devel] Re: [PATCH 0/5] Refactor and enhance RTC configuration Anthony Liguori
2009-09-09 16:24 ` Jan Kiszka
2009-09-09 16:41 ` Jan Kiszka
2009-09-09 18:03 ` Markus Armbruster
2009-09-09 17:59 ` Anthony Liguori
2009-09-09 20:00 ` Jan Kiszka
2009-09-09 20:18 ` Anthony Liguori [this message]
2009-09-09 22:23 ` Jamie Lokier
2009-09-11 8:54 ` Jan Kiszka
2009-09-13 15:08 ` Dor Laor
2009-09-13 15:37 ` Jan Kiszka
2009-09-14 13:36 ` Anthony Liguori
2009-09-14 15:40 ` Jan Kiszka
2009-09-09 17:59 ` Markus Armbruster
2009-09-10 10:41 ` Gerd Hoffmann
2009-09-09 17:33 ` Blue Swirl
2009-09-09 19:13 ` Jan Kiszka
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=4AA80DAE.8030006@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=dlaor@redhat.com \
--cc=glommer@redhat.com \
--cc=jan.kiszka@web.de \
--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.