[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b52b5e28-5805-4614-97cf-278610e2c574@zmail15.collab.prod.int.phx2.redhat.com>
Date: Wed, 23 Nov 2011 14:45:23 -0500 (EST)
From: Dave Anderson <anderson@...hat.com>
To: prasad@...ux.vnet.ibm.com
Cc: Vivek Goyal <vgoyal@...hat.com>, Borislav Petkov <bp@...en8.de>,
Tony Luck <tony.luck@...el.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
tachibana@....nes.nec.co.jp, oomichi@....nes.nec.co.jp,
Valdis Kletnieks <Valdis.Kletnieks@...edu>,
Nick Bowler <nbowler@...iptictech.com>,
linux-kernel@...r.kernel.org
Subject: Re: [RFC Patch 1/2][slimdump] Append CRASH_REASON to VMCOREINFO elf-note
----- Original Message -----
> On Mon, Nov 21, 2011 at 10:19:31AM -0500, Dave Anderson wrote:
> >
> >
> > ----- Original Message -----
> > > Allow various crash paths to append the reason of crash into the
> > > VMCOREINFO elf-note through the field CRASH_REASON. We also make the
> > > fatal machine check exceptions append "PANIC_MCE" as the crash
> > > reason. This string will be recognised by upstream tools like
> > > makedumpfile and crash to generate slimdump.
> >
> > I don't understand -- how could "various paths" append a reason?
> > The patch below seems to return "PANIC_MCE" for every x86 crash.
> > What am I missing?
> >
> > Dave
> >
>
> Yes, presently it can only be "PANIC_MCE" for MCE crashes in x86 (not
> for every crash though).
Why only MCE crashes? If your arch/x86/kernel/cpu/mcheck/mce.c is
compiled into any x86 kernel, then its arch_add_crash_reason() will
always override the weak version in kernel/kexec.c, right?
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists