From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MlSFI-0003zU-Nv
	for qemu-devel@nongnu.org; Wed, 09 Sep 2009 14:50:20 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MlSFD-0003xU-6t
	for qemu-devel@nongnu.org; Wed, 09 Sep 2009 14:50:19 -0400
Received: from [199.232.76.173] (port=35315 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MlSFD-0003xF-3R
	for qemu-devel@nongnu.org; Wed, 09 Sep 2009 14:50:15 -0400
Received: from mail-qy0-f172.google.com ([209.85.221.172]:62505)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1MlSFC-0006zA-Od
	for qemu-devel@nongnu.org; Wed, 09 Sep 2009 14:50:14 -0400
Received: by qyk2 with SMTP id 2so4110358qyk.21
	for <qemu-devel@nongnu.org>; Wed, 09 Sep 2009 11:50:14 -0700 (PDT)
Message-ID: <4AA7F8DD.7070807@codemonkey.ws>
Date: Wed, 09 Sep 2009 13:50:05 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [PATCH] re-set rtc date on reset handler
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> <20090909184043.GB30424@redhat.com>
In-Reply-To: <20090909184043.GB30424@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Gleb Natapov <gleb@redhat.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>

Gleb Natapov wrote:
> 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.
>   

You're right.

Regards,

Anthony Liguori