From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NjwzI-0004BQ-2c for qemu-devel@nongnu.org; Tue, 23 Feb 2010 10:47:52 -0500 Received: from [199.232.76.173] (port=44856 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NjwzH-0004B0-GB for qemu-devel@nongnu.org; Tue, 23 Feb 2010 10:47:51 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NjwzF-0001dq-Sr for qemu-devel@nongnu.org; Tue, 23 Feb 2010 10:47:51 -0500 Received: from mx20.gnu.org ([199.232.41.8]:49694) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NjwzF-0001ch-HB for qemu-devel@nongnu.org; Tue, 23 Feb 2010 10:47:49 -0500 Received: from bhuna.collabora.co.uk ([93.93.128.226]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NjwzA-0002eK-Kv for qemu-devel@nongnu.org; Tue, 23 Feb 2010 10:47:44 -0500 Message-ID: <4B83F86B.7070901@collabora.co.uk> Date: Tue, 23 Feb 2010 15:46:51 +0000 From: Ian Molton MIME-Version: 1.0 Subject: Re: [Qemu-devel] Address translation - virt->phys->ram References: <4B828DC2.3000609@collabora.co.uk> <4B829645.5020904@codemonkey.ws> <4B82B4E3.2040805@collabora.co.uk> <4B82B655.2000408@codemonkey.ws> <4B82C325.5020300@collabora.co.uk> <4B82D37B.2040906@suse.de> In-Reply-To: <4B82D37B.2040906@suse.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: cam@cs.ualberta.ca, qemu-devel@nongnu.org Alexander Graf wrote: > I guess what you really want is some shm region between host and guess > that you can use as ring buffer. Then you could run a timer on the host > side to flush it or have some sort of callback when you urgently need to > flush it manually. > > The benefit here is that you can actually make use of multiple threads. > There's no need to intercept the guest at all just because it wants to > issue some GL operations. Something like that should work. The problem right now is mostly the 'some sort of callback'. Im not sure there exists any mechanism for the guests userspace to interrupt qemu directly when running under kvm...