RFC Slimdump framework using CRASH_REASON - v2
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 12 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | Append CRASH_REASON to VMCOREINFO elf-notearch/ kernel/ | +14 | 8 replies | |
| 2/2 | Recognise PANIC_MCE crashes to generate slimduelf_info.c elf_info.h makedumpfile.c +1 more | +82 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [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