[Patch 00/12] Support Fujitsu Stand Arone Dump Format

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

 



Hello Tachibana san,

Sorry for the delayed patchs since the first CFI.

It's no problem on your plan. I'm waiting for your answer.

Thanks.
HATAYAMA, Daisuke

From: tachibana@xxxxxxxxxxxxxxxxx
Subject: Re: [Patch 00/12] Support Fujitsu Stand Arone Dump Format
Date: Wed, 12 Oct 2011 11:30:16 +0900

> Hi HATAYAMA-san,
> 
> Thank you for the patches.  I'll read them.
> However, I am busy now, so I'll answer in November.
> 
> 
> Thanks,
> tachibana
> 
> On 2011/10/12 00:13:38 +0900, HATAYAMA Daisuke <d.hatayama at jp.fujitsu.com> wrote:
>> The following series implements Fujitsu stand-alone dump (sadump)
>> format support for makedumpfile, converting sadump-related formats
>> into kdump-compressed format.
>> 
>> Based on makedumpfile version 1.4.0.
>> 
>> Here is summary of the changes.
>> 
>> No debug information on sadump-related formats
>> ==============================================
>> 
>> Unlike other dump mechanisms, VMCORE created by sadump has NO debug
>> information including VMCOREINFO. So, -x VMLINUX is definitely
>> necessary.
>> 
>> Debug information gained from VMLINUX is used for:
>> 
>>     1. creating VMCOREINFO dynamically, saved in resulting dumpfiles
>>        in kdump-compressed format, and
>> 
>>     2. gaining symbolic and type information necessary to refer to ELF
>>        note information contained in VMCORE generated by kdump at
>>        crash, and to estimate phys_base value.
>> 
>> If no VMLINUX is specified, dumpfile with no VMCOREINFO and ELF note
>> is generated on the current implementation.
>> 
>> 
>> Command-line interface change
>> =============================
>> 
>> Introduce --diskset=VMCORE to pass multiple VMCOREs in a single
>> commnad-line input.
>> 
>>     makedumpfile [OPTION] -x VMLINUX --diskset=VMCORE1 --diskset=VMCORE2 \
>>     [--diskset=VMCORE3 ..] DUMPFILE
>> 
>> 
>> Architectures
>> =============
>> 
>> X86 and X86_64.
>> 
>> On the other unsupported architectures, sadump-related source files
>> are never compiled and linked into makedumpfile executable.
>> 
>> ---
>> 
>> HATAYAMA Daisuke (12):
>>       Add description of sadump-related formats in manual page
>>       Add description of sadump-related formts in usage information
>>       Generate and save VMCOREINFO and ELF note information
>>       Estimate phys_base based on linux_banner position
>>       Implement readmem() interface on sadump-related formats
>>       Initialize debug information for ELF note extraction
>>       Initialize internal data according to sadump-related formats
>>       Export helpers for bitmap table handling
>>       Verify and read VMCORE(s) in sadump-related formats
>>       Implement command-line processing
>>       Extend DumpInfo structure
>>       Add sadump module header file
>> 
>> 
>>  Makefile       |    6 
>>  elf_info.c     |    2 
>>  makedumpfile.8 |   22 +
>>  makedumpfile.c |  397 ++++++++++---
>>  makedumpfile.h |  163 +++++
>>  print_info.c   |   10 
>>  sadump_info.c  | 1713 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>  sadump_info.h  |  159 +++++
>>  sadump_mod.h   |  186 ++++++
>>  9 files changed, 2578 insertions(+), 80 deletions(-)
>>  create mode 100644 sadump_info.c
>>  create mode 100644 sadump_info.h
>>  create mode 100644 sadump_mod.h
>> 
>> -- 
>> Thanks,
>> HATAYAMA, Daisuke
>> 
>> 
>> _______________________________________________
>> kexec mailing list
>> kexec at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/kexec
> 




[Index of Archives]     [LM Sensors]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux