From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:39329)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <wency@cn.fujitsu.com>) id 1S8R7C-0007Yi-Fd
	for qemu-devel@nongnu.org; Fri, 16 Mar 2012 02:58:19 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <wency@cn.fujitsu.com>) id 1S8R74-0007D7-Fd
	for qemu-devel@nongnu.org; Fri, 16 Mar 2012 02:58:18 -0400
Received: from [222.73.24.84] (port=58564 helo=song.cn.fujitsu.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <wency@cn.fujitsu.com>) id 1S8R74-0007Cv-4B
	for qemu-devel@nongnu.org; Fri, 16 Mar 2012 02:58:10 -0400
Message-ID: <4F62E4EF.7090907@cn.fujitsu.com>
Date: Fri, 16 Mar 2012 14:59:59 +0800
From: Wen Congyang <wency@cn.fujitsu.com>
MIME-Version: 1.0
References: <4F5FFC63.3060300@cn.fujitsu.com>	<4F5FFD74.1060102@cn.fujitsu.com>
	<20120316.153838.488343690.d.hatayama@jp.fujitsu.com>
In-Reply-To: <20120316.153838.488343690.d.hatayama@jp.fujitsu.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [Qemu-devel] [RFC][PATCH 05/14 v9] Add API to get memory mapping
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: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Cc: jan.kiszka@siemens.com, anderson@redhat.com, qemu-devel@nongnu.org, eblake@redhat.com, lcapitulino@redhat.com

At 03/16/2012 02:38 PM, HATAYAMA Daisuke Wrote:
> From: Wen Congyang <wency@cn.fujitsu.com>
> Subject: [RFC][PATCH 05/14 v9] Add API to get memory mapping
> Date: Wed, 14 Mar 2012 10:07:48 +0800
> 
>> Add API to get all virtual address and physical address mapping.
>> If the guest doesn't use paging, the virtual address is equal to the phyical
>> address. The virtual address and physical address mapping is for gdb's user, and
>> it does not include the memory that is not referenced by the page table. So if
>> you want to use crash to anaylze the vmcore, please do not specify -p option.
> 
> It's necessary to write the reason why the -p option is not default
> explicitly: guest machine in a catastrophic state can have corrupted
> memory, which we cannot trust.

Yes

Thanks
Wen Congyang

> 
> Thanks.
> HATAYAMA, Daisuke
> 
>