From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:38558) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QNLbj-0005Pz-PA for qemu-devel@nongnu.org; Fri, 20 May 2011 05:03:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QNLbY-0006Ns-Hf for qemu-devel@nongnu.org; Fri, 20 May 2011 05:02:55 -0400 Received: from mx1.redhat.com ([209.132.183.28]:21956) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QNLbY-0006No-1G for qemu-devel@nongnu.org; Fri, 20 May 2011 05:02:44 -0400 Message-ID: <4DD62E01.5010600@redhat.com> Date: Fri, 20 May 2011 12:01:53 +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> <4DD52B0E.2080604@codemonkey.ws> <4DD52BF2.2080506@redhat.com> <4DD54611.6090505@codemonkey.ws> In-Reply-To: <4DD54611.6090505@codemonkey.ws> 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: Anthony Liguori Cc: Jan Kiszka , qemu-devel , Gleb Natapov On 05/19/2011 07:32 PM, Anthony Liguori wrote: >> Think of how a window manager folds windows with priorities onto a flat >> framebuffer. >> >> You do a depth-first walk of the tree. For each child list, you iterate >> it from the lowest to highest priority, allowing later subregions >> override earlier subregions. >> > > > Okay, but this doesn't explain how you'll let RAM override the VGA > mapping since RAM is not represented in the same child list as VGA > (RAM is a child of the PMC whereas VGA is a child of ISA/PCI, both of > which are at least one level removed from the PMC). VGA will override RAM. Memory controller | +-- RAM container (prio 0) | +-- PCI container (prio 1) | +--- vga window -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.