From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MlPjS-0005kJ-KZ for qemu-devel@nongnu.org; Wed, 09 Sep 2009 12:09:18 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MlPjO-0005jc-4L for qemu-devel@nongnu.org; Wed, 09 Sep 2009 12:09:18 -0400 Received: from [199.232.76.173] (port=60730 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MlPjN-0005jZ-Ur for qemu-devel@nongnu.org; Wed, 09 Sep 2009 12:09:14 -0400 Received: from mx1.redhat.com ([209.132.183.28]:32615) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MlPjN-0003kk-FM for qemu-devel@nongnu.org; Wed, 09 Sep 2009 12:09:13 -0400 Date: Wed, 9 Sep 2009 19:09:06 +0300 From: Gleb Natapov Subject: Re: [Qemu-devel] Re: [PATCH] re-set rtc date on reset handler Message-ID: <20090909160906.GH22885@redhat.com> References: <4AA68310.1050209@siemens.com> <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AA7CB1E.8040409@us.ibm.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Jan Kiszka , Glauber Costa , "dlaor@redhat.com" , "qemu-devel@nongnu.org" , Blue Swirl , Avi Kivity On Wed, Sep 09, 2009 at 10:34:54AM -0500, Anthony Liguori wrote: > Avi Kivity wrote: > >On 09/09/2009 04:31 PM, Jan Kiszka wrote: > >>'drift-compensation-for-windows-guests' - this is at least what the > >>documentation suggests right now. I was looking for a short tag (but not > >>as short as 'td'...). > >> > > > >It would work for any guest that uses rtc as its main clock source. > > First step is qdev conversion for the RTC. You can then introduce a > drift property. I'd suggest something like > drift=none|catchup|gradual. The default can be none. We can also > introduce a kvm machine type where the default is catchup. > Obviously, we don't support gradual today. > What is "catchup" and what is "gradual"? -- Gleb.