qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] qdev: Introduce lost tick policy property
Date: Mon, 23 Jan 2012 20:01:55 +0000	[thread overview]
Message-ID: <20120123200155.GA7286@redhat.com> (raw)
In-Reply-To: <b4a4da9c3ce17f84278c489549ea5f7be8f4321c.1327346110.git.jan.kiszka@siemens.com>

On Mon, Jan 23, 2012 at 08:15:11PM +0100, Jan Kiszka wrote:
> Potentially tick-generating timer devices will gain a common property:
> lock_tick_policy. It allows to encode 4 different ways how to deal with
> tick events the guest did not process in time:
> 
> discard - ignore lost ticks (e.g. if the guest compensates for them
>           already)
> delay   - replay all lost ticks in a row once the guest accepts them
>           again
> merge   - if multiple ticks are lost, all of them are merged into one
>           which is replayed once the guest accepts it again
> slew    - lost ticks are gradually replayed at a higher frequency than
>           the original tick
> 
> Not all timer device will need to support all modes. However, all need
> to accept the configuration via this common property.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

That looks good - thank you for making the effort to come up with
something that maps so well to the libvirt model for this concept.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2012-01-23 20:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-23 19:15 [Qemu-devel] [PATCH 0/2] Generic tick reinjection control Jan Kiszka
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 [this message]
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=20120123200155.GA7286@redhat.com \
    --to=berrange@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.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).