From: "Martin J. Bligh" <mbligh@mbligh.org>
To: Kirill Korotaev <dev@sw.ru>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NMI lockup and AltSysRq-P dumping calltraces on _all_ cpus via NMI IPI
Date: Mon, 16 May 2005 15:34:15 -0700 [thread overview]
Message-ID: <768860000.1116282855@flay> (raw)
In-Reply-To: <42822B5F.8040901@sw.ru>
--On Wednesday, May 11, 2005 19:57:19 +0400 Kirill Korotaev <dev@sw.ru> wrote:
> against 2.6.12-rc4
>
> This patch adds dumping of calltraces on _all_ CPUs
> on AltSysRq-P and NMI LOCKUP. It does this via sending
> NMI IPI interrupts to the cpus.
>
> I saw the same patch in RedHat kernels, here goes our own version of the patch, not sure it will be accepted, but I think it can be used by some people at least for debugging lockups etc.
I'd done a similar thing, but just using smp_call_function (I hacked the
interrupt routine to fish pt_regs back out, and override *info in some
cases). Doing NMIs, as you've done, is probably nicer, but a lot more
work.
The problem with it (and my patch too) is that you're hooking into arch
specific code from generic code, which means you'll break every other
arch apart from i386. Fixing this is a pain in the rear end, but would
be needed to merge the patch. OTOH, the patch is extremely useful, so
would be nice to fix if you have the energy ...
M.
next prev parent reply other threads:[~2005-05-16 22:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 15:57 [PATCH] NMI lockup and AltSysRq-P dumping calltraces on _all_ cpus via NMI IPI Kirill Korotaev
2005-05-16 22:34 ` Martin J. Bligh [this message]
2005-05-17 7:04 ` [PATCH] NMI watchdog config option (was: Re: [PATCH] NMI lockup and AltSysRq-P dumping calltraces on _all_ cpus via NMI IPI) Kirill Korotaev
2005-05-17 7:15 ` Andrew Morton
2005-05-17 10:41 ` Kirill Korotaev
2005-05-17 14:01 ` Martin J. Bligh
2005-05-17 22:16 ` Andrew Morton
2005-05-17 22:26 ` Martin J. Bligh
2005-05-17 17:30 ` Valdis.Kletnieks
2005-05-17 15:48 ` Linus Torvalds
2005-05-17 15:59 ` Maciej W. Rozycki
2005-05-17 16:32 ` Linus Torvalds
2005-05-17 17:04 ` Maciej W. Rozycki
2005-05-17 17:20 ` Linus Torvalds
2005-05-17 17:44 ` Maciej W. Rozycki
2005-05-17 17:25 ` Valdis.Kletnieks
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=768860000.1116282855@flay \
--to=mbligh@mbligh.org \
--cc=akpm@osdl.org \
--cc=dev@sw.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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