From: Randy Dunlap <randy.dunlap@oracle.com>
To: Rik van Riel <riel@redhat.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
lwoodman@redhat.com
Subject: Re: [PATCH] sysrq show-all-cpus
Date: Mon, 10 Mar 2008 11:09:09 -0700 [thread overview]
Message-ID: <47D57945.60204@oracle.com> (raw)
In-Reply-To: <20080310140315.1a451092@bree.surriel.com>
Rik van Riel wrote:
> SysRQ-P is not always useful on SMP systems, since it usually ends up showing the
> backtrace of a CPU that is doing just fine, instead of the backtrace of the CPU
> that is having problems.
>
> This patch adds SysRQ show-all-cpus(L), which shows the backtrace of every active
> CPU in the system. It skips idle CPUs because some SMP systems are just too large
> and we already know what the backtrace of the idle task looks like.
>
> Signed-off-by: Rik van Riel <riel@redhat.com>
>
> diff -up linux-2.6.25-rc3-mm1/Documentation/sysrq.txt.multicpu linux-2.6.25-rc3-mm1/Documentation/sysrq.txt
> --- linux-2.6.25-rc3-mm1/Documentation/sysrq.txt.multicpu 2008-03-10 13:49:18.000000000 -0400
> +++ linux-2.6.25-rc3-mm1/Documentation/sysrq.txt 2008-03-10 13:51:09.000000000 -0400
> @@ -85,6 +85,8 @@ On all - write a character to /proc/sys
> 'k' - Secure Access Key (SAK) Kills all programs on the current virtual
> console. NOTE: See important comments below in SAK section.
>
> +'l' - Shows a stack backtrace for all active CPUs.
> +
> 'm' - Will dump current memory info to your console.
>
> 'n' - Used to make RT tasks nice-able
Yep, thanks.
A diffstat is also appreciated (in the future).
--
~Randy
next prev parent reply other threads:[~2008-03-10 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 17:32 [PATCH] sysrq show-all-cpus Rik van Riel
2008-03-10 17:41 ` Andrew Morton
2008-03-10 17:57 ` Rik van Riel
2008-03-10 17:46 ` Randy Dunlap
2008-03-10 18:03 ` Rik van Riel
2008-03-10 18:09 ` Randy Dunlap [this message]
2008-03-11 7:18 ` Jon Masters
2008-03-11 14:07 ` Rik van Riel
2008-03-11 15:06 ` Jon Masters
2008-03-11 8:12 ` Nick Piggin
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=47D57945.60204@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lwoodman@redhat.com \
--cc=riel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.