Yes, I intent to put duplicate mapping for kernel code and data in kexec-tools 
to help both region 5 and region 7 trace on kernel text and data works.

Thank
Zou Nan hai
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 2006年12月1日 3:07
> To: [EMAIL PROTECTED]
> Cc: kexec kdump redhat mailing list; [email protected]; Zou, Nanhai
> Subject: Re: duplicate section in ia64 vmcore from kdump
> 
> Bob Montgomery wrote:
> 
> > Has this been discussed and I missed it?
> >
> > I'm seeing a duplicate LOAD section from /proc/vmcore as shown in this
> > excerpt from readelf -l vmcore:
> >
> > Program Headers:
> >   Type           Offset             VirtAddr           PhysAddr
> >                  FileSiz            MemSiz              Flags  Align
> >  ...
> >   LOAD           0x0000000000001f08 0xe000000000001000 0x0000000000001000
> >                  0x0000000003fff000 0x0000000003fff000  RWE    0
> >
> > >>  LOAD         0x0000000004000f08 0xa000000100000000 0x0000000004000000
> >                  0x0000000000d46000 0x0000000000d46000  RWE    0
> >
> > >>  LOAD         0x0000000004d46f08 0xe000000004000000 0x0000000004000000
> >                  0x0000000000d46000 0x0000000000d46000  RWE    0
> >
> >   LOAD           0x0000000005a8cf08 0xe000000004d46000 0x0000000004d46000
> >                  0x00000000032ba000 0x00000000032ba000  RWE    0
> > ...
> >
> > Note the two sections with PhysAddr x0000000004000000,
> > one at VirtAddr=0xa000000100000000, and the other at
> > VirtAddr=0xe000000004000000.  They are at different offsets
> > in the file, and using objdump -s --section=loadN, I believe
> > they contain identical data.  It's a lot of redundant data
> > in the dump file.  I assume the problem is in the purgatory
> > code that sets up the elf map?  Is it necessary to include
> > this section with both of its virtual aliases for some reason?
> >
> > Bob Montgomery
> 
> It's necessary for both the crash utility and gdb to work.  The ia64
> region 5 descriptor contains the physical base address where the
> relocatable kernel was loaded, needed by the crash utility.  And
> it's needed for gdb because it deals with virtual addresses in
> that region for kernel text and static data.
> 
> And yes, it has been discussed on the fastboot list, starting here:
> 
>   http://lists.osdl.org/pipermail/fastboot/2006-November/004948.html
> 
> Dave

_______________________________________________
fastboot mailing list
[email protected]
https://lists.osdl.org/mailman/listinfo/fastboot

Reply via email to