From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:42949)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <wency@cn.fujitsu.com>) id 1RGKrF-0005Hv-Dh
	for qemu-devel@nongnu.org; Tue, 18 Oct 2011 21:22:14 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <wency@cn.fujitsu.com>) id 1RGKr6-0001xD-R8
	for qemu-devel@nongnu.org; Tue, 18 Oct 2011 21:22:07 -0400
Received: from [222.73.24.84] (port=51721 helo=song.cn.fujitsu.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <wency@cn.fujitsu.com>) id 1RGKqu-0001vi-HJ
	for qemu-devel@nongnu.org; Tue, 18 Oct 2011 21:22:04 -0400
Message-ID: <4E9E2684.5050108@cn.fujitsu.com>
Date: Wed, 19 Oct 2011 09:23:16 +0800
From: Wen Congyang <wency@cn.fujitsu.com>
MIME-Version: 1.0
References: <20111010090246.GF9408@redhat.com>
	<4E92BC11.3030508@siemens.com>	<4E9D2791.5070207@cn.fujitsu.com>
	<4E9D3059.7050903@siemens.com>	<4E9D31B4.1010000@cn.fujitsu.com>
	<4E9D3678.3010904@siemens.com>	<4E9D3804.5040000@cn.fujitsu.com>
	<4E9D3847.8040202@siemens.com>	<4E9D3965.4090003@cn.fujitsu.com>
	<4E9D394E.6050907@siemens.com>	<20111018083416.GL8872@amd.home.annexia.org>	<4E9D3A80.10402@siemens.com>
	<4E9D4A2D.1070907@cn.fujitsu.com>	<4E9D54E4.80802@siemens.com>
	<4E9D8459.5060803@gmail.com>	<4E9D8544.5070405@siemens.com>
	<4E9D8A71.6070805@gmail.com>	<4E9D8B74.1000802@siemens.com>
	<4E9D9562.7080309@gmail.com> <4E9D9AE8.6040507@siemens.com>
In-Reply-To: <4E9D9AE8.6040507@siemens.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [Qemu-devel] [Question] dump memory when host pci device is
 used by guest
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: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Wen Congyang <wencongyang@gmail.com>, "Richard W.M. Jones" <rjones@redhat.com>, qemu-devel <qemu-devel@nongnu.org>

At 10/18/2011 11:27 PM, Jan Kiszka Write:
> On 2011-10-18 17:04, Wen Congyang wrote:
>> On 10/18/2011 10:21 PM, Jan Kiszka wrote:
>>> On 2011-10-18 16:17, Wen Congyang wrote:
>>>
>>> I was talking about information you need in the crash dump file that is
>>> not contained in those files crash processes by default. If there is no
>>> such information, then it looks strange to me defining a new format.
>>
>> Sorry for my bad english, I can not understant what information you are
>> talking about.
>>
>> Do you mean if the core file does not contains such information and crash
>> can not process it?
> 
> OK, I guess we are just talking past each other:
> 
> Are you proposing the kernel dump format (as crash takes for its
> "dumpfile" parameter)? Should QEMU write out dumps in that file format?

Yes.

We can reuse gdbstub's code, and use gdb scripts to instead of crash. But
I do not like this way, because we should know the guest kernel version
and it's config file. We should do too many things that crash has done
for us.

So I think qemu should write out dumps in that file format.

Thanks
Wen Congyang

> 
> Jan
>