Re: [PATCH] documentation: update sysrq.txt key mappings

[Alexander Shishkin]

On Tue, Sep 21, 2010 at 04:01:42 -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
> 
> 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@xxxxxxxxxx>
> Cc:	Jason Wessel <jason.wessel@xxxxxxxxxxxxx>
> Cc:	"David S. Miller" <davem@xxxxxxxxxxxxx>
> Cc:	"James E.J. Bottomley" <James.Bottomley@xxxxxxx>
> Cc:	David Airlie <airlied@xxxxxxxx>
> Cc:	Alexander Shishkin <virtuoso@xxxxxxxxx>

Acked-by: Alexander Shishkin <virtuoso@xxxxxxxxx>

> ---
>  Documentation/sysrq.txt |    7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> --- lnx-2636-rc5.orig/Documentation/sysrq.txt
> +++ lnx-2636-rc5/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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/