From: Gleb Natapov <gleb@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Glauber Costa <glommer@redhat.com>,
"dlaor@redhat.com" <dlaor@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Blue Swirl <blauwirbel@gmail.com>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH] re-set rtc date on reset handler
Date: Wed, 9 Sep 2009 21:40:43 +0300 [thread overview]
Message-ID: <20090909184043.GB30424@redhat.com> (raw)
In-Reply-To: <4AA7EB4C.205@us.ibm.com>
On Wed, Sep 09, 2009 at 12:52:12PM -0500, Anthony Liguori wrote:
> Gleb Natapov wrote:
> >What is "catchup" and what is "gradual"?
>
> Just placeholders to point out that there are different algorithms
> to replaying interrupts to a guest. I called what we implemented
> "catchup" since we pretty much immediately send all of the missed
> ticks to the guest in order to catch-up.
>
> I'd imagine that a 'gradual' algorithm would shorten the tick
> interval until you've caught up. The Hyper-V paravirtualization
> manual has provisions for the guest to request what type of
> algorithm is used so it makes sense to accommodate this in our
> syntax.
>
We implement gradual then.
--
Gleb.
next prev parent reply other threads:[~2009-09-09 18:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 16:22 [Qemu-devel] [PATCH] re-set rtc date on reset handler Glauber Costa
2009-09-01 16:56 ` Blue Swirl
2009-09-01 23:00 ` Glauber Costa
2009-09-08 14:55 ` Dor Laor
2009-09-08 16:15 ` [Qemu-devel] " Jan Kiszka
2009-09-08 16:50 ` Jan Kiszka
2009-09-08 17:00 ` Jan Kiszka
2009-09-09 12:28 ` Dor Laor
2009-09-09 12:57 ` Jan Kiszka
2009-09-09 13:27 ` Avi Kivity
2009-09-09 13:31 ` Jan Kiszka
2009-09-09 15:04 ` Avi Kivity
2009-09-09 15:34 ` Anthony Liguori
2009-09-09 16:09 ` Gleb Natapov
2009-09-09 17:52 ` Anthony Liguori
2009-09-09 18:40 ` Gleb Natapov [this message]
2009-09-09 18:50 ` Anthony Liguori
2009-09-09 18:25 ` Avi Kivity
2009-09-09 18:33 ` 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=20090909184043.GB30424@redhat.com \
--to=gleb@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=dlaor@redhat.com \
--cc=glommer@redhat.com \
--cc=jan.kiszka@siemens.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 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.