From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:58729)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1QNOKX-0006eq-8Q
	for qemu-devel@nongnu.org; Fri, 20 May 2011 07:57:22 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1QNOKW-0004P1-AG
	for qemu-devel@nongnu.org; Fri, 20 May 2011 07:57:21 -0400
Received: from mx1.redhat.com ([209.132.183.28]:56183)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1QNOKW-0004Ot-0o
	for qemu-devel@nongnu.org; Fri, 20 May 2011 07:57:20 -0400
Date: Fri, 20 May 2011 14:57:16 +0300
From: Gleb Natapov <gleb@redhat.com>
Message-ID: <20110520115716.GN27310@redhat.com>
References: <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>
	<20110519162706.GB27310@redhat.com> <4DD62D8E.2010605@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4DD62D8E.2010605@redhat.com>
Subject: Re: [Qemu-devel] [RFC] Memory API
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Avi Kivity <avi@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel <qemu-devel@nongnu.org>

On Fri, May 20, 2011 at 11:59:58AM +0300, Avi Kivity wrote:
> On 05/19/2011 07:27 PM, Gleb Natapov 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.
> >>
> >I do not think that window manager is a good analogy. Window can
> >overlap with only its siblings. In our memory tree each final node may
> >overlap with any other node in the tree.
> >
> 
> Transparent windows.
> 
No, still not that. Think about child windows that resides outside of its
parent windows on screen. In our memory region terms think about PCI BAR
is registered to overlap with RAM at address 0x1000 for instance. PCI
BAR memory region and RAM memory region are on very different branches
of the global tree.

--
			Gleb.