[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111121095405.GA2289@in.ibm.com>
Date: Mon, 21 Nov 2011 15:24:05 +0530
From: "K.Prasad" <prasad@...ux.vnet.ibm.com>
To: linux-kernel@...r.kernel.org
Cc: Vivek Goyal <vgoyal@...hat.com>, Borislav Petkov <bp@...en8.de>,
"Luck, Tony" <tony.luck@...el.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>, anderson@...hat.com,
tachibana@....nes.nec.co.jp, oomichi@....nes.nec.co.jp,
Valdis.Kletnieks@...edu, Nick Bowler <nbowler@...iptictech.com>
Subject: [RFC Patch 0/2] Slimdump framework using CRASH_REASON - v2
Hi All,
In furtherance of the previous discussion regarding 'slimdump'
(refer: http://article.gmane.org/gmane.linux.kernel/1204967), it was
decided that,
- An entry in VMCOREINFO elf-note be added to denote the cause of crash,
instead of creating a new elf-note.
- Upstream tools such as 'makedumpfile' and 'crash' be modified to
recognise this string and inform the user accordingly.
Accordingly, this new version of the patchset makes the following
changes
Changelog - version 2
-----------------------
(First version posted here:
http://article.gmane.org/gmane.linux.kernel/1198435)
- Append VMCOREINFO elf-note with a new variable CRASH_REASON whose
value will be populated using arch_add_crash_reason() function.
- Define arch_add_crash_reason() in the x86 MCE path to return "PANIC_MCE"
in the panic path of MCE.
- 'makedumpfile' tool is taught to recognise PANIC_MCE string as one
value of CRASH_REASON for which 'slimdump' must be captured.
- Changes to 'crash' tool are not included, and is deferred till there's
consensus to the kernel and makedumpfile patches.
Let me know your comments on this.
Thanks,
K.Prasad
--
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