From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LP5Uk-0001c4-HZ for qemu-devel@nongnu.org; Mon, 19 Jan 2009 20:33:34 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LP5Uh-0001bM-JN for qemu-devel@nongnu.org; Mon, 19 Jan 2009 20:33:34 -0500 Received: from [199.232.76.173] (port=48885 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LP5Uh-0001bG-Gm for qemu-devel@nongnu.org; Mon, 19 Jan 2009 20:33:31 -0500 Received: from mx20.gnu.org ([199.232.41.8]:1734) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LP5Uh-00067U-7q for qemu-devel@nongnu.org; Mon, 19 Jan 2009 20:33:31 -0500 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LP5Uf-0006wn-8I for qemu-devel@nongnu.org; Mon, 19 Jan 2009 20:33:29 -0500 From: Paul Brook Date: Tue, 20 Jan 2009 01:33:23 +0000 References: <20090119162633.GO29175@csclub.uwaterloo.ca> <20090119194221.GS29175@csclub.uwaterloo.ca> <20090120005351.GV29175@csclub.uwaterloo.ca> In-Reply-To: <20090120005351.GV29175@csclub.uwaterloo.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901200133.25029.paul@codesourcery.com> Subject: [Qemu-devel] Extremely slow graphic updates (was: qemu-system-ppc seems slow today) 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 Cc: Stefano Stabellini , Lennart Sorensen > 'ssh -X fastserver' and running qemu there. With the new display code > this has made qemu very slow and hardly useable. I'm seeing similar extreme slowness even on a local machine. Particularly noticeable is that the monitor displayed on a qemu virtual SDL console (i.e. the defaut) slow enough to be practically unusable. It's taking the best part of a second to rendering a character. This is on an otherwise fast machine that does not have accelerated X drivers, which suggests we're doing something really dumb like reading from video ram. I have confirmed that this is caused by r6336. Paul