From: Jason Wessel <jason.wessel@windriver.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
torvalds <torvalds@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
"James E.J. Bottomley" <James.Bottomley@suse.de>,
David Airlie <airlied@linux.ie>,
Alexander Shishkin <virtuoso@slind.org>
Subject: Re: [PATCH] documentation: update sysrq.txt magic sysrq keys
Date: Tue, 26 Oct 2010 20:36:30 -0500 [thread overview]
Message-ID: <4CC7821E.9070503@windriver.com> (raw)
In-Reply-To: <20101026142040.2f0b70a1.randy.dunlap@oracle.com>
Acked-by: Jason Wessel <jason.wessel@windriver.com>
If you take a look at commit: 364b5b7b1d793a7f98be55b6b154716dcae78dfc,
the voyager and kgdb bits were originally fixed there. It was not
obvious to me at the time that this was documented in multiple places,
else it would have been fixed in the same commit.
Cheers,
Jason.
On 10/26/2010 04:20 PM, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Update Documentation/sysrq.txt magic sysrq keys:
>
> - 'g' is for kgdb (not arch-specific);
> - add 2 new uses for 'v', remove the Voyager info;
> - add 'y' info (SPARC-64 specific);
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> Cc: Jason Wessel <jason.wessel@windriver.com>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: "James E.J. Bottomley" <James.Bottomley@suse.de>
> Cc: David Airlie <airlied@linux.ie>
> Acked-by: Alexander Shishkin <virtuoso@slind.org>
> ---
> Documentation/sysrq.txt | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> --- lnx-2636-g6-docs.orig/Documentation/sysrq.txt
> +++ lnx-2636-g6-docs/Documentation/sysrq.txt
> @@ -75,7 +75,7 @@ On all - write a character to /proc/sys
>
> 'f' - Will call oom_kill to kill a memory hog process.
>
> -'g' - Used by kgdb on ppc and sh platforms.
> +'g' - Used by kgdb (kernel debugger)
>
> 'h' - Will display help (actually any other key than those listed
> here will display help. but 'h' is easy to remember :-)
> @@ -110,12 +110,15 @@ On all - write a character to /proc/sys
>
> 'u' - Will attempt to remount all mounted filesystems read-only.
>
> -'v' - Dumps Voyager SMP processor info to your console.
> +'v' - Forcefully restores framebuffer console
> +'v' - Causes ETM buffer dump [ARM-specific]
>
> 'w' - Dumps tasks that are in uninterruptable (blocked) state.
>
> 'x' - Used by xmon interface on ppc/powerpc platforms.
>
> +'y' - Show global CPU Registers [SPARC-64 specific]
> +
> 'z' - Dump the ftrace buffer
>
> '0'-'9' - Sets the console log level, controlling which kernel messages
>
prev parent reply other threads:[~2010-10-27 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 21:20 [PATCH] documentation: update sysrq.txt magic sysrq keys Randy Dunlap
2010-10-27 1:36 ` Jason Wessel [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=4CC7821E.9070503@windriver.com \
--to=jason.wessel@windriver.com \
--cc=James.Bottomley@suse.de \
--cc=airlied@linux.ie \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.org \
--cc=virtuoso@slind.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