lkml.org 
[lkml]   [2011]   [Jun]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC Patch 4/6] PANIC_MCE: Introduce a new panic flag for fatal MCE, capture related information


----- Original Message -----
> On Wed, Jun 01, 2011 at 01:18:16PM -0400, Dave Anderson wrote:
> > FWIW, unlike mcelog, it really doesn't have to be maintained in the crash
> > utility. It's just another kernel data structure whose contents can be
> > determined dynamically during runtime:
> >
>
> That's what I was wondering. Why can't we simple extract the contents
> of this structure from /proc/vmcore and save it, instead of trying to
> export it by appending additional elf notes to vmcore.

Actually I take that back -- Prasad's patch looks at the ELF header
contents and exits before the crash utility invokes the embedded gdb,
so the structure contents are unavailable at that time. It doesn't even
use the vmlinux file.

Dave

>
> Thanks
> Vivek
>
> > crash> struct mce
> > struct mce {
> > __u64 status;
> > __u64 misc;
> > __u64 addr;
> > __u64 mcgstatus;
> > __u64 ip;
> > __u64 tsc;
> > __u64 time;
> > __u8 cpuvendor;
> > __u8 inject_flags;
> > __u16 pad;
> > __u32 cpuid;
> > __u8 cs;
> > __u8 bank;
> > __u8 cpu;
> > __u8 finished;
> > __u32 extcpu;
> > __u32 socketid;
> > __u32 apicid;
> > __u64 mcgcap;
> > }
> > SIZE: 88
> > crash>
> >
> > Dave
> >
> > > If you think that this complicates the patch, I'll start with a
> > > much
> > > 'slimmer' version (!) of the slimdump and the improvements may be
> > > contemplated iteratively.
> > >
> > > Thanks,
> > > K.Prasad


\
 
 \ /
  Last update: 2011-06-01 19:43    [W:0.048 / U:0.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site