From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MlS69-0003fp-OL
	for qemu-devel@nongnu.org; Wed, 09 Sep 2009 14:40:53 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MlS65-0003dC-Vt
	for qemu-devel@nongnu.org; Wed, 09 Sep 2009 14:40:53 -0400
Received: from [199.232.76.173] (port=44553 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MlS65-0003d2-NT
	for qemu-devel@nongnu.org; Wed, 09 Sep 2009 14:40:49 -0400
Received: from mx1.redhat.com ([209.132.183.28]:36244)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <gleb@redhat.com>) id 1MlS65-0005Sq-9J
	for qemu-devel@nongnu.org; Wed, 09 Sep 2009 14:40:49 -0400
Date: Wed, 9 Sep 2009 21:40:43 +0300
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH] re-set rtc date on reset handler
Message-ID: <20090909184043.GB30424@redhat.com>
References: <4AA68B50.8000805@siemens.com> <4AA68DBB.9080000@siemens.com>
	<4AA79F67.9060401@redhat.com> <4AA7A61C.4050902@siemens.com>
	<4AA7AD43.30000@redhat.com> <4AA7AE45.6050104@siemens.com>
	<4AA7C411.9050008@redhat.com> <4AA7CB1E.8040409@us.ibm.com>
	<20090909160906.GH22885@redhat.com> <4AA7EB4C.205@us.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4AA7EB4C.205@us.ibm.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
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>

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.