qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	Glauber Costa <glommer@redhat.com>, Dor Laor <dlaor@redhat.com>,
	qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 0/5] Refactor and enhance RTC configuration
Date: Wed, 09 Sep 2009 10:40:22 -0500	[thread overview]
Message-ID: <4AA7CC66.5060008@us.ibm.com> (raw)
In-Reply-To: <20090909151111.26816.49862.stgit@mchn012c.ww002.siemens.net>

Jan Kiszka wrote:
> The aim of this series is to allow using the emulated PC RTC (MC146818)
> as a reliable time source for guests. This is particularly useful if the
> host runs NTP or has otherwise access to an accurate clock while the
> guest has not (no network, impossible to add an NTP implementation
> etc.).
>
> To achieve this, the command line switch -rtc is introduced. It takes
> the option 'clock' to switch between the currently used base ('vm') and
> the new QEMU_CLOCK_HOST ('host'). At this chance, -rtc is also used to
> deprecate all the other RTC-related stand-alone switches.
>
> First tests indicate that this approach works as expected and could
> increase the usefulness of the virtual RTC enormously. However, there
> might be pitfalls I've missed so far. Feedback would be welcome!
>   

You get most of this pretty cheaply with qdev conversion.  If you give 
the rtc a default id, you can tweak all of the properties with the -set 
command line option.  It also provides a mechanism to change the default 
properties between machine types/versions which is ideal as we can 
introduce a kvm-specific machine type where we enable some of these 
things by default.

-- 
Regards,

Anthony Liguori

  parent reply	other threads:[~2009-09-09 15:40 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 1/5] Rename QEMU_TIMER_* to QEMU_CLOCK_* 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 5/5] Enable host-clock-based RTC 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 3/5] Introduce QEMU_CLOCK_HOST Jan Kiszka
2009-09-09 15:40 ` Anthony Liguori [this message]
2009-09-09 16:24   ` [Qemu-devel] Re: [PATCH 0/5] Refactor and enhance RTC configuration 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
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=4AA7CC66.5060008@us.ibm.com \
    --to=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 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).