From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:51921) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R32AC-0003ln-Cc for qemu-devel@nongnu.org; Mon, 12 Sep 2011 04:46:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R32AB-0007dx-Fg for qemu-devel@nongnu.org; Mon, 12 Sep 2011 04:46:48 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55498) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R32AB-0007dt-4m for qemu-devel@nongnu.org; Mon, 12 Sep 2011 04:46:47 -0400 Message-ID: <4E6DC6F2.1020407@redhat.com> Date: Mon, 12 Sep 2011 11:46:42 +0300 From: Avi Kivity MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: Blue Swirl Cc: qemu-devel 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. I originally wanted to implement this via a gdb script. This works even when all you have is a core dump. But I can see it's useful on a live system. -- error compiling committee.c: too many arguments to function