From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HXQjW-0006gS-Ef for qemu-devel@nongnu.org; Fri, 30 Mar 2007 19:42:14 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HXQjU-0006gF-Un for qemu-devel@nongnu.org; Fri, 30 Mar 2007 19:42:14 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HXQjU-0006gC-PA for qemu-devel@nongnu.org; Fri, 30 Mar 2007 18:42:12 -0500 Received: from nz-out-0506.google.com ([64.233.162.227]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HXQgk-0005IO-6O for qemu-devel@nongnu.org; Fri, 30 Mar 2007 19:39:22 -0400 Received: by nz-out-0506.google.com with SMTP id i11so1178174nzi for ; Fri, 30 Mar 2007 16:39:21 -0700 (PDT) Message-ID: Date: Sat, 31 Mar 2007 01:39:20 +0200 From: "andrzej zaborowski" Sender: balrogg@gmail.com Subject: Re: [Qemu-devel] [PATCH] add a simple 24mhz clock for the versatile In-Reply-To: <7ED098B05D69FE41B380586BF1474DBA22D651@ala-mail08.corp.ad.wrs.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7ED098B05D69FE41B380586BF1474DBA22D651@ala-mail08.corp.ad.wrs.com> Reply-To: balrogg@gmail.com, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 31/03/07, Wessel, Jason wrote: > > > uint64_t now = qemu_get_clock(vm_clock); > return (uint32_t)((now*3)/125); > > The optimizer should fix this up with no floating point ops. Adding to the bikeshed discussion (www.bikeshed.com) this is still not correct as vm_clock is to be used with ticks_per_sec. return muldiv64(qemu_get_clock(vm_clock), 24000000, ticks_per_sec); Regards, Andrzej