From: Don Zickus <dzickus@redhat.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: akpm@linux-foundation.org, x86@kernel.org, davem@davemloft.net,
sparclinux@vger.kernel.org, mguzik@redhat.com,
Don Zickus <dzickus@redhat.com>
Subject: [PATCH 0/4 V3] Print traces on softlockup
Date: Tue, 22 Apr 2014 11:17:24 -0400 [thread overview]
Message-ID: <1398179848-197479-1-git-send-email-dzickus@redhat.com> (raw)
Added more patches to handle the 'uniprocessor' panic case by sending NMIs
to every cpu but self. Only affects x86, sparc.
V3: wrap x86 code with get/put_cpu based on Oleg's suggestions
V2: expand from one patch to 4
Aaron Tomlin (4):
nmi: Provide the option to issue an NMI back trace to every cpu but
current
x86, nmi: Add more flexible NMI back trace support
sparc64, nmi: Add more flexible NMI back trace support
watchdog: Printing traces for all cpus on lockup detection
Documentation/kernel-parameters.txt | 5 +++++
Documentation/sysctl/kernel.txt | 17 +++++++++++++++++
arch/sparc/include/asm/irq_64.h | 2 +-
arch/sparc/kernel/process_64.c | 14 +++++++++-----
arch/x86/include/asm/irq.h | 2 +-
arch/x86/kernel/apic/hw_nmi.c | 17 +++++++++++++----
include/linux/nmi.h | 12 +++++++++++-
kernel/sysctl.c | 9 +++++++++
kernel/watchdog.c | 32 ++++++++++++++++++++++++++++++++
9 files changed, 98 insertions(+), 12 deletions(-)
next reply other threads:[~2014-04-22 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 15:17 Don Zickus [this message]
2014-04-22 15:17 ` [PATCH 1/4 v3] nmi: Provide the option to issue an NMI back trace to every cpu but current Don Zickus
2014-04-22 15:17 ` [PATCH 2/4 v3] x86, nmi: Add more flexible NMI back trace support Don Zickus
2014-04-22 15:17 ` [PATCH 3/4 v3] sparc64, " Don Zickus
2014-04-22 15:17 ` [PATCH 4/4 v3] watchdog: Printing traces for all cpus on lockup detection Don Zickus
2014-04-22 18:28 ` [PATCH 0/4 V3] Print traces on softlockup Andrew Morton
2014-04-22 19:09 ` Don Zickus
2014-04-23 19:22 ` Don Zickus
2014-04-23 19:35 ` Andrew Morton
2014-04-23 20:44 ` Don Zickus
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=1398179848-197479-1-git-send-email-dzickus@redhat.com \
--to=dzickus@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mguzik@redhat.com \
--cc=sparclinux@vger.kernel.org \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®