From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:43323) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QN4G3-0001VS-J2 for qemu-devel@nongnu.org; Thu, 19 May 2011 10:31:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QN4G2-0000Bg-JB for qemu-devel@nongnu.org; Thu, 19 May 2011 10:31:23 -0400 Received: from mx1.redhat.com ([209.132.183.28]:40102) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QN4G2-0000Ba-4n for qemu-devel@nongnu.org; Thu, 19 May 2011 10:31:22 -0400 Message-ID: <4DD529B3.7030606@redhat.com> Date: Thu, 19 May 2011 17:31:15 +0300 From: Avi Kivity MIME-Version: 1.0 References: <4DD3D236.90708@siemens.com> <4DD3D95E.2060105@redhat.com> <4DD3E1B3.3020405@siemens.com> <4DD3E47F.9060104@redhat.com> <4DD3E782.8090208@siemens.com> <4DD3E8D6.6090807@redhat.com> <20110519090851.GD28399@redhat.com> <4DD4DE8E.8030402@redhat.com> <20110519091404.GE28399@redhat.com> <4DD5029D.6000700@redhat.com> <20110519115405.GG28399@redhat.com> <4DD505C4.6010604@redhat.com> <4DD50B17.7000205@siemens.com> <4DD511FB.3080901@redhat.com> <4DD51413.1050202@siemens.com> <4DD51468.7050509@redhat.com> <4DD51531.7000701@siemens.com> <4DD515F9.1020902@redhat.com> <4DD51A82.7060205@siemens.com> <4DD51B64.8000306@redhat.com> <4DD51FDA.3010107@codemonkey.ws> <4DD520ED.8010606@redhat.com> <4DD5260A.1080309@codemonkey.ws> <4DD5272F.5000003@siemens.com> <4DD52848.6030102@codemonkey.ws> <4DD52910.4080106@siemens.com> In-Reply-To: <4DD52910.4080106@siemens.com> Content-Type: text/plain; charset=ISO-8859-1; 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: Gleb Natapov , qemu-devel On 05/19/2011 05:28 PM, Jan Kiszka wrote: > >> > >> Priorities would be local, so the normal tree would look like this: > >> > >> - CPU:0 > >> - i440fx:0 > >> - PIIX3:0 > >> - DeviceA > >> - PCI-DeviceB:0 > >> > >> If the i440fx would like to map something different over DeviceA (or > >> parts of it), it would create a region of prio 1 or higher. > > > > If it's local, then you need a local dispatch table, no? > > Not working for the coalescing reason pointed out before. + RAM (including framebuffers) > It's also more > handy to rely on the core to do the proper dispatching then write your > own logic over and over again. The core has to deal with overlapping anyway. Plus, to reiterate, if you have the information you can calculate a flattened global dispatch table taking into account all offsets and priorities. -- error compiling committee.c: too many arguments to function