From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] Generic tick reinjection control
Date: Mon, 23 Jan 2012 20:15:10 +0100 [thread overview]
Message-ID: <cover.1327346110.git.jan.kiszka@siemens.com> (raw)
QEMU currently supports lost tick compensation for the periodic RTC
timer. It is controlled via -rtc driftfix=slew|none. However, the next
periodic timer with compensation qualities is approaching: KVM's
in-kernel PIT.
A previous discussion [1] showed that we need to introduce per device
control. And we likely also want a global default. Both features require
a generic standardized way to specify the compensation mode.
So this series lays the ground for that by adding a qdev property type
to select from four possible lost tick compensation policies (see patch
1 one for details). And this new property is then applied on the RTC
device.
[1] http://thread.gmane.org/gmane.comp.emulators.kvm.devel/85339
Jan Kiszka (2):
qdev: Introduce lost tick policy property
mc146818rtc: Use lost_tick_policy property
hw/mc146818rtc.c | 26 +++++++++++++++++------
hw/qdev-properties.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++++++
hw/qdev.h | 7 ++++++
qemu-common.h | 7 ++++++
sysemu.h | 1 -
vl.c | 28 ++++++++++++++++++++----
6 files changed, 111 insertions(+), 13 deletions(-)
--
1.7.3.4
next reply other threads:[~2012-01-23 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 19:15 Jan Kiszka [this message]
2012-01-23 19:15 ` [Qemu-devel] [PATCH 1/2] qdev: Introduce lost tick policy property Jan Kiszka
2012-01-23 20:01 ` Daniel P. Berrange
2012-01-23 19:15 ` [Qemu-devel] [PATCH 2/2] mc146818rtc: Use lost_tick_policy property Jan Kiszka
2012-01-23 19:24 ` [Qemu-devel] [PATCH 0/2] Generic tick reinjection control Anthony Liguori
2012-02-01 22:10 ` 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=cover.1327346110.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=mtosatti@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 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).