From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:42415) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QMypN-0003Vx-CK for qemu-devel@nongnu.org; Thu, 19 May 2011 04:43:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QMypM-0008MF-Cw for qemu-devel@nongnu.org; Thu, 19 May 2011 04:43:29 -0400 Received: from mx1.redhat.com ([209.132.183.28]:62418) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QMypM-0008M4-4e for qemu-devel@nongnu.org; Thu, 19 May 2011 04:43:28 -0400 Message-ID: <4DD4D82B.90301@redhat.com> Date: Thu, 19 May 2011 11:43:23 +0300 From: Avi Kivity MIME-Version: 1.0 References: <4DD3C5B9.1080908@redhat.com> <4DD420A5.2020606@web.de> <4DD4CF76.2080904@redhat.com> <4DD4CFF5.6040805@web.de> <4DD4D137.3030605@redhat.com> <4DD4D402.5000606@web.de> In-Reply-To: <4DD4D402.5000606@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: qemu-devel On 05/19/2011 11:25 AM, Jan Kiszka wrote: > > > > Unspecified doesn't mean abort. It means we need to specify something > > (which translates to: we get to pick the priorities). > > Of course, PCI bars would have to be registered via > cpu_register_memory_region_overlap, just specifying the default > priority. Here we know that overlapping can happen and is not a bug in > the board emulation. I want to avoid that such use cases make > overlapping generally legal, papering over real bugs. But those are the majority of regions. There are a few extra RAM and ROM and fixed function regions, but these are hardly likely to clash. -- error compiling committee.c: too many arguments to function