From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:51264) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QN3PL-0001vY-CX for qemu-devel@nongnu.org; Thu, 19 May 2011 09:36:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QN3PK-0007g4-E3 for qemu-devel@nongnu.org; Thu, 19 May 2011 09:36:55 -0400 Received: from mail-yi0-f45.google.com ([209.85.218.45]:49142) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QN3PK-0007fx-AS for qemu-devel@nongnu.org; Thu, 19 May 2011 09:36:54 -0400 Received: by yib19 with SMTP id 19so1046575yib.4 for ; Thu, 19 May 2011 06:36:53 -0700 (PDT) Message-ID: <4DD51CF3.5040306@codemonkey.ws> Date: Thu, 19 May 2011 08:36:51 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <4DD3C5B9.1080908@redhat.com> <4DD420A5.2020606@web.de> In-Reply-To: <4DD420A5.2020606@web.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC] Memory API List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Avi Kivity , qemu-devel 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. Regards, Anthony Liguori > We need that ordering, so we need an interface. Regions registered via > cpu_register_memory_region must not overlap with existing one or we will > throw an hwerror. And they shall get a low default priority. > > Jan >