From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ESLly-0004rj-Tq for qemu-devel@nongnu.org; Wed, 19 Oct 2005 17:46:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ESLly-0004rV-4I for qemu-devel@nongnu.org; Wed, 19 Oct 2005 17:46:58 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ESLlx-0004rS-Uz for qemu-devel@nongnu.org; Wed, 19 Oct 2005 17:46:57 -0400 Received: from [128.8.10.163] (helo=po1.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1ESLly-0007Fo-4c for qemu-devel@nongnu.org; Wed, 19 Oct 2005 17:46:58 -0400 Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.253.219]) by po1.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j9JLktgW004753 for ; Wed, 19 Oct 2005 17:46:55 -0400 (EDT) Date: Wed, 19 Oct 2005 17:46:50 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] kqemu processor feature question Message-ID: <20051019214650.GA25061@jbrown.mylinuxbox.org> References: <20051018184347.93934.qmail@web50514.mail.yahoo.com> <1129669383.5865.61.camel@aragorn> <43556663.9090203@wasp.net.au> <200510192023.47943.qemu-devel@pellereau.net> <43569A6F.7070002@wasp.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43569A6F.7070002@wasp.net.au> Reply-To: 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 Wed, Oct 19, 2005 at 11:11:43PM +0400, Brad Campbell wrote: > It is off.. that is my issue.. Not quite sure what is going on .. > Anyway.. the -no-tsc patch works around my issue, but there is still > something wierd going on with > my tsc. > > Regards, > Brad > -- > "Human beings, who are almost unique in having the ability > to learn from the experience of others, are also remarkable > for their apparent disinclination to do so." -- Douglas Adams qemu uses an unreliable timesource, the rdtsc instruction. That works most of the time but is not a good idea when CPU usage varies a lot. I'm not suprised at the difference across cpus either. I'm not sure if kqemu has an effect on this or not (but if it does, kernel code would probably have slower ticks that user mode code). -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.