From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:36724) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R32GS-0005NG-3x for qemu-devel@nongnu.org; Mon, 12 Sep 2011 04:53:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R32GQ-0000c9-W7 for qemu-devel@nongnu.org; Mon, 12 Sep 2011 04:53:16 -0400 Received: from thoth.sbs.de ([192.35.17.2]:32932) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R32GQ-0000bc-Mk for qemu-devel@nongnu.org; Mon, 12 Sep 2011 04:53:14 -0400 Message-ID: <4E6DC874.8080009@siemens.com> Date: Mon, 12 Sep 2011 10:53:08 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4E6DC6F2.1020407@redhat.com> In-Reply-To: <4E6DC6F2.1020407@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] memory: simple memory tree printer List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Blue Swirl , qemu-devel On 2011-09-12 10:46, Avi Kivity wrote: > On 09/11/2011 11:31 PM, Blue Swirl wrote: >> Add a monitor command 'info mtree' to show the memory hierarchy. >> > > Does this turn the memory hierarchy into an ABI? It shouldn't. Things > like BARs are immutable but if a BAR is internally composed of several > regions, well that's no one's business. "info mtree" falls into the same category as "info qtree" or "device_show": they expose useful but unstable internal structures. But they also only exist for the human monitor, so their output is not an ABI by our definition. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux