From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:58913) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QNRhW-0000Nc-Fe for qemu-devel@nongnu.org; Fri, 20 May 2011 11:33:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QNRhV-0007IQ-JN for qemu-devel@nongnu.org; Fri, 20 May 2011 11:33:18 -0400 Received: from mail-yx0-f173.google.com ([209.85.213.173]:60249) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QNRhV-0007IM-Gs for qemu-devel@nongnu.org; Fri, 20 May 2011 11:33:17 -0400 Received: by yxk8 with SMTP id 8so1559947yxk.4 for ; Fri, 20 May 2011 08:33:16 -0700 (PDT) Message-ID: <4DD689BA.8020106@codemonkey.ws> Date: Fri, 20 May 2011 10:33:14 -0500 From: Anthony Liguori 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> <4DD62E01.5010600@redhat.com> In-Reply-To: <4DD62E01.5010600@redhat.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: Avi Kivity Cc: Jan Kiszka , qemu-devel , Gleb Natapov On 05/20/2011 04:01 AM, Avi Kivity wrote: > 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 Unless the RAM controller increases it's priority, right? That's how you would implement SMM, by doing priority++? But if you have: Memory controller | +-- RAM container (prio 0) | +-- PCI container (prio 1) | +-- PCI-X container (prio 2) | +--- vga window Now you need to do priority = 3? Jan had mentioned previously about registering a new temporary window. I assume the registration always gets highest_priority++, or do you have to explicitly specify that PCI container gets priority=1? Regards, Anthony Liguori > >