From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:53925) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QMzE0-0005sa-F7 for qemu-devel@nongnu.org; Thu, 19 May 2011 05:08:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QMzDy-0004Ox-P4 for qemu-devel@nongnu.org; Thu, 19 May 2011 05:08:56 -0400 Received: from mx1.redhat.com ([209.132.183.28]:1028) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QMzDy-0004Ot-Gh for qemu-devel@nongnu.org; Thu, 19 May 2011 05:08:54 -0400 Date: Thu, 19 May 2011 12:08:51 +0300 From: Gleb Natapov Message-ID: <20110519090851.GD28399@redhat.com> References: <4DD3C5B9.1080908@redhat.com> <4DD3D236.90708@siemens.com> <4DD3D95E.2060105@redhat.com> <4DD3E1B3.3020405@siemens.com> <4DD3E47F.9060104@redhat.com> <4DD3E782.8090208@siemens.com> <4DD3E8D6.6090807@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DD3E8D6.6090807@redhat.com> Subject: Re: [Qemu-devel] [RFC] Memory API List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Jan Kiszka , qemu-devel On Wed, May 18, 2011 at 06:42:14PM +0300, Avi Kivity wrote: > On 05/18/2011 06:36 PM, Jan Kiszka wrote: > >> > >> We need to head for the more hardware-like approach. What happens when > >> you program overlapping BARs? I imagine the result is > >> implementation-defined, but ends up with one region decoded in > >> preference to the other. There is simply no way to reject an > >> overlapping mapping. > > > >But there is also now simple way to allow them. At least not without > >exposing control about their ordering AND allowing to hook up managing > >code (e.g. of the PCI bridge or the chipset) that controls registrations. > > What about memory_region_add_subregion(..., int priority) as I > suggested in another message? Haven't saw another message yet, but how caller knows about priority? -- Gleb.