From: Vitaly Mayatskikh <v.mayatskih@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Vivek Goyal <vgoyal@redhat.com>,
Randy Dunlap <rdunlap@xenotime.net>
Subject: [PATCH 0/5] kdump: extract log buffer and registers from vmcore on NMI button pressing
Date: Wed, 2 Jun 2010 09:39:14 +0200 [thread overview]
Message-ID: <1275464359-1566-1-git-send-email-v.mayatskih@gmail.com> (raw)
Sometimes non-interactive dump capture environment silently fails to
store vmcore due to hardware or software bug. It is hard then to
understand and fix reasons of system failure in both production and
dump capture environments to prevent this failure to reoccur. It would
be quite usefull to see log buffer contents of crashed kernel at
least.
This patchset adds possibility for dump capture mode to extract and
print log buffer and CPU registers from captured vmcore. Also the
state of running kernel is printed. This action can be triggered via
NMI button.
Signed-off-by: Vitaly Mayatskikh <v.mayatskih@gmail.com>
arch/x86/include/asm/elf.h | 46 +++++
arch/x86/include/asm/kdebug.h | 1 +
arch/x86/include/asm/nmi.h | 1 +
arch/x86/kernel/apic/nmi.c | 27 +++
arch/x86/kernel/process_32.c | 22 ++-
arch/x86/kernel/process_64.c | 20 ++-
fs/proc/vmcore.c | 365 +++++++++++++++++++++++++++++++++++++++--
include/linux/sysctl.h | 1 +
kernel/sysctl.c | 7 +
kernel/sysctl_binary.c | 1 +
10 files changed, 463 insertions(+), 28 deletions(-)
next reply other threads:[~2010-06-02 9:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 7:39 Vitaly Mayatskikh [this message]
2010-06-02 7:39 ` [PATCH 1/5] x86: Introduce ELF_CORE_EXTRACT_REGS Vitaly Mayatskikh
2010-06-02 7:39 ` [PATCH 2/5] x86: Split __show_regs() Vitaly Mayatskikh
2010-06-02 9:50 ` Pekka Enberg
2010-06-02 10:00 ` Vitaly Mayatskikh
2010-06-02 7:39 ` [PATCH 3/5] vmcore: Introduce dump_old_log() Vitaly Mayatskikh
2010-06-02 7:39 ` [PATCH 4/5] x86: Add new callback for unhandled NMIs Vitaly Mayatskikh
2010-06-02 7:39 ` [PATCH 5/5] Document unknown_nmi_dump_log variable Vitaly Mayatskikh
2010-06-02 15:16 ` [PATCH 0/5] kdump: extract log buffer and registers from vmcore on NMI button pressing Vivek Goyal
2010-06-03 9:01 ` Vitaly Mayatskikh
2010-06-03 9:30 ` Andi Kleen
2010-06-03 12:33 ` Vitaly Mayatskikh
2010-06-03 15:13 ` Andi Kleen
2010-06-04 9:32 ` Vitaly Mayatskikh
2010-06-04 10:15 ` Andi Kleen
2010-06-04 13:58 ` Vitaly Mayatskikh
2010-06-04 9:49 ` Américo Wang
2010-06-04 10:16 ` Andi Kleen
2010-06-04 14:49 ` Vivek Goyal
2010-06-04 14:42 ` Vivek Goyal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1275464359-1566-1-git-send-email-v.mayatskih@gmail.com \
--to=v.mayatskih@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@xenotime.net \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).