linux魔法键抢占优先级,magic sysrq -- 魔术键的使用，linux下使用

最经典的文档

---------------------------

Linux Magic System Request Key HacksDocumentation for sysrq.c*  What is the magic SysRq key?~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~It is a 'magical' key combo you can hit which the kernel will respond toregardless of whatever else it is doing, unless it is completely locked up.*  How do I enable the magic SysRq key?~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~You need to say "yes" to 'Magic SysRq key (CONFIG_MAGIC_SYSRQ)' whenconfiguring the kernel. When running a kernel with SysRq compiled in,/proc/sys/kernel/sysrq controls the functions allowed to be invoked viathe SysRq key. By default the file contains 1 which means that everypossible SysRq request is allowed (in older versions SysRq was disabledby default, and you were required to specifically enable it at run-timebut this is not the case any more). Here is the list of possible valuesin /proc/sys/kernel/sysrq:0 - disable sysrq completely1 - enable all functions of sysrq>1 - bitmask of allowed sysrq functions (see below for detailed functiondescription):2 - enable control of console logging level4 - enable control of keyboard (SAK, unraw)8 - enable debugging dumps of processes etc.16 - enable sync command32 - enable remount read-only64 - enable signalling of processes (term, kill, oom-kill)128 - allow reboot/poweroff256 - allow nicing of all RT tasksYou can set the value in the file by the following command:echo "number" >/proc/sys/kernel/sysrqNote that the value of /proc/sys/kernel/sysrq influences only the invocationvia a keyboard. Invocation of any operation via /proc/sysrq-trigger is alwaysallowed (by a user with admin privileges).*  How do I use the magic SysRq key?~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~On x86   - You press the key combo 'ALT-SysRq-'. Note - Somekeyboards may not have a key labeled 'SysRq'. The 'SysRq' key isalso known as the 'Print Screen' key. Also some keyboards cannothandle so many keys being pressed at the same time, so you mighthave better luck with "press Alt", "press SysRq", "release SysRq","press ", release everything.On SPARC - You press 'ALT-STOP-', I believe.On the serial console (PC style standard serial ports only) -You send a BREAK, then within 5 seconds a command key. SendingBREAK twice is interpreted as a normal BREAK.On PowerPC - Press 'ALT - Print Screen (or F13) - ,Print Screen (or F13) - may suffice.On other - If you know of the key combos for other architectures, pleaselet me know so I can add them to this section.On all -  write a character to /proc/sysrq-trigger.  e.g.:echo t > /proc/sysrq-trigger*  What are the 'command' keys?~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'b'     - Will immediately reboot the system without syncing or unmountingyour disks.'c'- Will perform a system crash by a NULL pointer dereference.A crashdump will be taken if configured.'d'- Shows all locks that are held.'e'     - Send a SIGTERM to all processes, except for init.'f'- Will call oom_kill to kill a memory hog process.'g'- Used by kgdb (kernel debugger)'h'     - Will display help (actually any other key than those listedhere will display help. but 'h' is easy to remember :-)'i'     - Send a SIGKILL to all processes, except for init.'j'     - Forcibly "Just thaw it" - filesystems frozen by the FIFREEZE ioctl.'k'     - Secure Access Key (SAK) Kills all programs on the current virtualconsole. 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'o'     - Will shut your system off (if configured and supported).'p'     - Will dump the current registers and flags to your console.'q'     - Will dump per CPU lists of all armed hrtimers (but NOT regulartimer_list timers) and detailed information about allclockevent devices.'r'     - Turns off keyboard raw mode and sets it to XLATE.'s'     - Will attempt to sync all mounted filesystems.'t'     - Will dump a list of current tasks and their information to yourconsole.'u'     - Will attempt to remount all mounted filesystems read-only.'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 messageswill be printed to your console. ('0', for example would makeit so that only emergency messages like PANICs or OOPSes wouldmake it to your console.)*  Okay, so what can I use them for?~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Well, un'R'aw is very handy when your X server or a svgalib program crashes.sa'K' (Secure Access Key) is useful when you want to be sure there is notrojan program running at console which could grab your passwordwhen you would try to login. It will kill all programs on given console,thus letting you make sure that the login prompt you see is actuallythe one from init, not some trojan program.IMPORTANT: In its true form it is not a true SAK like the one in a :IMPORTANTIMPORTANT: c2 compliant system, and it should not be mistaken as   :IMPORTANTIMPORTANT: such.                                                   :IMPORTANTIt seems others find it useful as (System Attention Key) which isuseful when you want to exit a program that will not let you switch consoles.(For example, X or a svgalib program.)re'B'oot is good when you're unable to shut down. But you should also 'S'yncand 'U'mount first.'C'rash can be used to manually trigger a crashdump when the system is hung.Note that this just triggers a crash if there is no dump mechanism available.'S'ync is great when your system is locked up, it allows you to sync yourdisks and will certainly lessen the chance of data loss and fscking. Notethat the sync hasn't taken place until you see the "OK" and "Done" appearon the screen. (If the kernel is really in strife, you may not ever get theOK or Done message...)'U'mount is basically useful in the same ways as 'S'ync. I generally 'S'ync,'U'mount, then re'B'oot when my system locks. It's saved me many a fsck.Again, the unmount (remount read-only) hasn't taken place until you see the"OK" and "Done" message appear on the screen.The loglevels '0'-'9' are useful when your console is being flooded withkernel messages you do not want to see. Selecting '0' will prevent all butthe most urgent kernel messages from reaching your console. (They willstill be logged if syslogd/klogd are alive, though.)t'E'rm and k'I'll are useful if you have some sort of runaway process youare unable to kill any other way, especially if it's spawning otherprocesses."'J'ust thaw it" is useful if your system becomes unresponsive due to a frozen(probably root) filesystem via the FIFREEZE ioctl.*  Sometimes SysRq seems to get 'stuck' after using it, what can I do?~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~That happens to me, also. I've found that tapping shift, alt, and controlon both sides of the keyboard, and hitting an invalid sysrq sequence againwill fix the problem. (i.e., something like alt-sysrq-z). Switching to anothervirtual console (ALT+Fn) and then back again should also help.*  I hit SysRq, but nothing seems to happen, what's wrong?~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~There are some keyboards that produce a different keycode for SysRq than thepre-defined value of 99 (see KEY_SYSRQ in include/linux/input.h), or whichdon't have a SysRq key at all. In these cases, run 'showkey -s' to find anappropriate scancode sequence, and use 'setkeycodes 99' to mapthis sequence to the usual SysRq code (e.g., 'setkeycodes e05b 99'). It'sprobably best to put this command in a boot script. Oh, and by the way, youexit 'showkey' by not typing anything for ten seconds.*  I want to add SysRQ key events to a module, how does it work?~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~In order to register a basic function with the table, you must first includethe header 'include/linux/sysrq.h', this will define everything else you need.Next, you must create a sysrq_key_op struct, and populate it with A) the keyhandler function you will use, B) a help_msg string, that will print when SysRQprints help, and C) an action_msg string, that will print right before yourhandler is called. Your handler must conform to the prototype in 'sysrq.h'.After the sysrq_key_op is created, you can call the kernel functionregister_sysrq_key(int key, struct sysrq_key_op *op_p); this willregister the operation pointed to by 'op_p' at table key 'key',if that slot in the table is blank. At module unload time, you must callthe function unregister_sysrq_key(int key, struct sysrq_key_op *op_p), whichwill remove the key op pointed to by 'op_p' from the key 'key', if and only ifit is currently registered in that slot. This is in case the slot has beenoverwritten since you registered it.The Magic SysRQ system works by registering key operations against a key oplookup table, which is defined in 'drivers/char/sysrq.c'. This key table hasa number of operations registered into it at compile time, but is mutable,and 2 functions are exported for interface to it:register_sysrq_key and unregister_sysrq_key.Of course, never ever leave an invalid pointer in the table. I.e., whenyour module that called register_sysrq_key() exits, it must callunregister_sysrq_key() to clean up the sysrq key table entry that it used.Null pointers in the table are always safe. :)If for some reason you feel the need to call the handle_sysrq function fromwithin a function called by handle_sysrq, you must be aware that you are ina lock (you are also in an interrupt handler, which means don't sleep!), soyou must call __handle_sysrq_nolock instead.*  When I hit a SysRq key combination only the header appears on the console?~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Sysrq output is subject to the same console loglevel control as allother console output.  This means that if the kernel was booted 'quiet'as is common on distro kernels the output may not appear on the actualconsole, even though it will appear in the dmesg buffer, and be accessiblevia the dmesg command and to the consumers of /proc/kmsg.  As a specificexception the header line from the sysrq command is passed to all consoleconsumers as if the current loglevel was maximum.  If only the headeris emitted it is almost certain that the kernel loglevel is too low.Should you require the output on the console channel then you will needto temporarily up the console loglevel using alt-sysrq-8 or:echo 8 > /proc/sysrq-triggerRemember to return the loglevel to normal after triggering the sysrqcommand you are interested in.*  I have more questions, who can I ask?~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~And I'll answer any questions about the registration system you got, alsoresponding as soon as possible.-Crutcher*  Credits~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Written by MydraalUpdated by Adam SulmickiUpdated by Jeremy M. Dolan 2001/01/28 10:15:59Added to by Crutcher Dunnavant