LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Rik van Riel <riel@redhat.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	lwoodman@redhat.com
Subject: Re: [PATCH] sysrq show-all-cpus
Date: Tue, 11 Mar 2008 19:12:54 +1100	[thread overview]
Message-ID: <200803111912.55075.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <20080310140315.1a451092@bree.surriel.com>

On Tuesday 11 March 2008 05:03, 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.
>

Yeah we need something like this. I prefer mine though ;) It shows
registers as well as stack...

http://groups.google.com.au/group/fa.linux.kernel/msg/3cd0288f7fd3be2c?dmode=source&output=gplain

It prints just a single CPU at a time, but cycles through each one.
An alternative might be to have one sysrq key used to cycle between
CPUs, and sysrq+P could then just print out a trace from the selected
CPU...



      parent reply	other threads:[~2008-03-11  8:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10 17:32 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
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 [this message]

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=200803111912.55075.nickpiggin@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwoodman@redhat.com \
    --cc=randy.dunlap@oracle.com \
    --cc=riel@redhat.com \
    --subject='Re: [PATCH] sysrq show-all-cpus' \
    /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

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).