From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LOyWr-0005Yg-E9 for qemu-devel@nongnu.org; Mon, 19 Jan 2009 13:07:17 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LOyWp-0005Xi-FZ for qemu-devel@nongnu.org; Mon, 19 Jan 2009 13:07:16 -0500 Received: from [199.232.76.173] (port=38143 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LOyWp-0005Xf-8y for qemu-devel@nongnu.org; Mon, 19 Jan 2009 13:07:15 -0500 Received: from caffeine.csclub.uwaterloo.ca ([129.97.134.17]:38624) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LOyWo-00074y-P2 for qemu-devel@nongnu.org; Mon, 19 Jan 2009 13:07:15 -0500 Received: from caffeine.csclub.uwaterloo.ca (localhost [127.0.0.1]) by caffeine.csclub.uwaterloo.ca (Postfix) with ESMTP id 695DD73E19 for ; Mon, 19 Jan 2009 13:07:14 -0500 (EST) Date: Mon, 19 Jan 2009 13:07:14 -0500 Subject: Re: [Qemu-devel] qemu-system-ppc seems slow today. Message-ID: <20090119180714.GR29175@csclub.uwaterloo.ca> References: <20090119162633.GO29175@csclub.uwaterloo.ca> <20090119170912.GH3461@hall.aurel32.net> <20090119174914.GP29175@csclub.uwaterloo.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090119174914.GP29175@csclub.uwaterloo.ca> From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen) 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 Mon, Jan 19, 2009 at 12:49:14PM -0500, Lennart Sorensen wrote: > Boot time of about a minute versus about 6 or 7 minutes. Seems to scale > completely with the drop in cpu usage. Use 1/6 of the cpu and run 6 > times slower. > > OK, I am trying to find how I can get the svn commit number from the > result of make -k tar. All I have found so far just says svn. > > I of course didn't keep the previous checkout since I just did svn > update in the same directory. > > Well there can't be that many commits in 5 days, so I should be able to > pick somewhere to start a bisect from. Hmm, so if I run 'watch -n 1 date' in qemu and on the host, in the time 10 seconds pass in qemu, 25 seconds passed on the host. qemu thinks it is running as fast as before, but its concept of real time is wrong. With the build I did on january 14th, the qemu and the host are in sync timewise and qemu is way more responsive (at the cost of a lot of cpu of course). -- Len Sorensen