From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LplKA-0001ra-JC for qemu-devel@nongnu.org; Fri, 03 Apr 2009 11:28:54 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LplK6-0001pl-1E for qemu-devel@nongnu.org; Fri, 03 Apr 2009 11:28:54 -0400 Received: from [199.232.76.173] (port=41886 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LplK5-0001pf-Pc for qemu-devel@nongnu.org; Fri, 03 Apr 2009 11:28:49 -0400 Received: from mx20.gnu.org ([199.232.41.8]:60099) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LplK5-0006oe-Eq for qemu-devel@nongnu.org; Fri, 03 Apr 2009 11:28:49 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LplK3-00032T-UX for qemu-devel@nongnu.org; Fri, 03 Apr 2009 11:28:48 -0400 From: Paul Brook Subject: Re: [Qemu-devel] PATCH/RFC: PCI memory mapping Date: Fri, 3 Apr 2009 15:28:45 +0000 References: <1238684238.18745.17.camel@nibbler.dlib.indiana.edu> <200904022340.35427.paul@codesourcery.com> <1238771149.28860.75.camel@nibbler.dlib.indiana.edu> In-Reply-To: <1238771149.28860.75.camel@nibbler.dlib.indiana.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200904031628.45716.paul@codesourcery.com> 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 > So, for example, a cirrus vga device on bus 1 when calling: > > cpu_register_physical_memory(addr, s->vram_size, > s->cirrus_linear_io_addr); Ah, that's a different (but somewhat related) problem. This is for accesses from the CPU to the device. Most current IOMMU effect device->CPU accesses[1]. Paul [1] For practical purposes assume the the CPU and system ram are on the same bus.