From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1JL3Vi-0000Gq-Fd
	for qemu-devel@nongnu.org; Fri, 01 Feb 2008 16:33:22 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1JL3Ve-0000Bm-U1
	for qemu-devel@nongnu.org; Fri, 01 Feb 2008 16:33:22 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1JL3Ve-0000BI-Mi
	for qemu-devel@nongnu.org; Fri, 01 Feb 2008 16:33:18 -0500
Received: from mail.codesourcery.com ([65.74.133.4])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1JL3Vd-0005UG-VJ
	for qemu-devel@nongnu.org; Fri, 01 Feb 2008 16:33:18 -0500
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [kvm-devel] [Qemu-devel] Re: [PATCH 1/6] Use correct types to
	enable > 2G support
Date: Fri, 1 Feb 2008 21:33:07 +0000
References: <1201818980-27534-1-git-send-email-aliguori@us.ibm.com>
	<20080201175750.GD22981@redhat.com>
	<47A381B9.1060707@codemonkey.ws>
In-Reply-To: <47A381B9.1060707@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200802012133.09400.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: kvm-devel@lists.sourceforge.net, Ian Jackson <Ian.Jackson@eu.citrix.com>

> virtio could still be made to work with map cache.  You would just have
> to change it to be able to map more than one page contiguously.  As I
> mentioned though, it just starts getting ugly.

That's why you should be using the cpu_physical_memory_rw routines :-)

Anything that assume large linear accesses (Currently only some of the 
embedded LCD controllers) is going to break as soon as you start introducing 
IOMMUs. There have been several threads on this list about having a sane DMA 
infrastructure.

Paul