qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [Question] dump memory when host pci device is used by


From: Jan Kiszka
Subject: Re: [Qemu-devel] [Question] dump memory when host pci device is used by guest
Date: Tue, 25 Oct 2011 09:37:15 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666

On 2011-10-25 03:37, Wen Congyang wrote:
> At 10/24/2011 11:58 PM, Dave Anderson Write:
>>
>>
>> ----- Original Message -----
>>
>>>>> No, an ELF image of the guest's physical memory.
>>>>
>>>> Well then that should be pretty straight forward to support.  Depending 
>>>> upon
>>>> how similar it would be to the "standard" kdump ELF format, the only other
>>>> issue is how to determine the physical base address at which the kernel is
>>>> loaded, in order to be able to translate the mapped kernel-text/static-data
>>>> virtual region of the x86_64 arch (the __START_KERNEL_map region).
>>>>
>>>
>>> I guess an elf note would work for that?
>>
>> Right -- here is an example of a RHEL6 ELF kdump header:
> 
> Hi, Jan
> Is gdb standard core file like the following format? Does gdb support this
> format?
> 
> If yes, I think the dump command can output the guest physical memory in
> the following format, and we can use both gdb and crash to analyze it.

That would be ideal. But given lacking crash-like add-ons for vanilla
gdb, it makes sense to focus on crash compatibility for now. I suspect
we will need some changes to gdb anyway to make use of all information
the kdump file contains.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux



reply via email to

[Prev in Thread] Current Thread [Next in Thread]