From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:36739) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QN3QQ-0003O7-Nh for qemu-devel@nongnu.org; Thu, 19 May 2011 09:38:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QN3QP-0007nD-RQ for qemu-devel@nongnu.org; Thu, 19 May 2011 09:38:02 -0400 Received: from david.siemens.de ([192.35.17.14]:28646) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QN3QP-0007mu-Fi for qemu-devel@nongnu.org; Thu, 19 May 2011 09:38:01 -0400 Message-ID: <4DD51D36.7040504@siemens.com> Date: Thu, 19 May 2011 15:37:58 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4DD3C5B9.1080908@redhat.com> <4DD420A5.2020606@web.de> <4DD51CF3.5040306@codemonkey.ws> In-Reply-To: <4DD51CF3.5040306@codemonkey.ws> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC] Memory API List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Avi Kivity , qemu-devel On 2011-05-19 15:36, Anthony Liguori wrote: > On 05/18/2011 02:40 PM, Jan Kiszka wrote: >> On 2011-05-18 15:12, Avi Kivity wrote: >>> void cpu_register_memory_region(MemoryRegion *mr, target_phys_addr_t >>> addr); >> >> OK, let's allow overlapping, but make it explicit: >> >> void cpu_register_memory_region_overlap(MemoryRegion *mr, >> target_phys_addr_t addr, >> int priority); > > The device doesn't actually know how overlapping is handled. This is > based on the bus hierarchy. Devices don't register their regions, buses do. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux