From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MlRqu-0008S3-K9 for qemu-devel@nongnu.org; Wed, 09 Sep 2009 14:25:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MlRqp-0008Ll-Nd for qemu-devel@nongnu.org; Wed, 09 Sep 2009 14:25:08 -0400 Received: from [199.232.76.173] (port=38976 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MlRqp-0008LY-FG for qemu-devel@nongnu.org; Wed, 09 Sep 2009 14:25:03 -0400 Received: from mx1.redhat.com ([209.132.183.28]:13263) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MlRqo-0002tt-B6 for qemu-devel@nongnu.org; Wed, 09 Sep 2009 14:25:02 -0400 Message-ID: <4AA7F313.2090208@redhat.com> Date: Wed, 09 Sep 2009 21:25:23 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH] re-set rtc date on reset handler References: <1251822154-5423-1-git-send-email-glommer@redhat.com> <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> In-Reply-To: <4AA7CB1E.8040409@us.ibm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Blue Swirl , Jan Kiszka , Glauber Costa , "dlaor@redhat.com" , "qemu-devel@nongnu.org" On 09/09/2009 06:34 PM, Anthony Liguori wrote: > 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. > Maybe none|step|slew to avoid alienating mayo lovers. Should be a global option that applies to all clock sources? -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.