From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EATA1-0003NQ-2z for qemu-devel@nongnu.org; Wed, 31 Aug 2005 10:01:53 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EAT9w-0003L6-3F for qemu-devel@nongnu.org; Wed, 31 Aug 2005 10:01:50 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EAT9u-0003Ii-UN for qemu-devel@nongnu.org; Wed, 31 Aug 2005 10:01:46 -0400 Received: from [66.54.152.27] (helo=jive.SoftHome.net) by monty-python.gnu.org with smtp (Exim 4.34) id 1EAT4P-0003RF-As for qemu-devel@nongnu.org; Wed, 31 Aug 2005 09:56:05 -0400 From: Mulyadi Santosa Subject: Re: Re: [Qemu-devel] Timing problems Date: Wed, 31 Aug 2005 19:19:02 +0700 References: <1125257033.24800.28.camel@linux.site> <200508291001.39221.a_mulyadi@softhome.net> <1125436100.9706.19.camel@linux> In-Reply-To: <1125436100.9706.19.camel@linux> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508311919.02083.a_mulyadi@softhome.net> Reply-To: a_mulyadi@softhome.net, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Sven Zenker , "Jim C. Brown" Cc: qemu-devel@nongnu.org Hello Sven... > rdtsc gives you the cpu's clock count, which, if CPU frequency > changes, or your code is run on different processors (multiprocessor > machine), cannot be assumed to be related to real time anymore. > Resolutionwise, the real time clock may be inferior, of course, as > Jim mentioned. Jim: could you point me to this other patch? Thanks! Oh, so sorry, I was mistakenly made conclusion about your patch. yes, you are correct, get_clock() will do the trick....while rdtsc won't work because the clock will run vary during speed-stepping.... The unified format of diff looks great! :) regards Mulyadi