From: Andi Kleen <ak@suse.de>
To: "Randy.Dunlap" <rddunlap@osdl.org>, Andi Kleen <ak@suse.de>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.5] speedup kallsyms_lookup
Date: Sat, 11 Jan 2003 05:28:18 +0100 [thread overview]
Message-ID: <20030111042818.GB10699@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0301101055030.19536-100000@dragon.pdx.osdl.net>
> Ctrl-ScrollLock on mine if I'm following you correctly.
> Same as Sysrq-P if sysrq is enabled, except that the former
> is always available.
Try Ctrl-,Alt/AltGr-,Shift- with the same key.
>
> Are there other similar functions that are available without
> Sysrq enabled? If so, where can I find info about them?
Quite a lot.
In your keymap. e.g. on a SuSE system.
getkeycodes will output a map of the key codes.
% less /usr/share/kbd/keymaps/i386/include/linux-keys-bare.inc
alt keycode 59 = Console_1
alt keycode 60 = Console_2
...
control alt keycode 59 = Console_1
control alt keycode 60 = Console_2
...
alt keycode 71 = Ascii_7
alt keycode 72 = Ascii_8
...
alt keycode 103 = KeyboardSignal
alt keycode 105 = Decr_Console
alt keycode 106 = Incr_Console
...
shift keycode 104 = Scroll_Backward
shift keycode 109 = Scroll_Forward
control alt keycode 111 = Boot
...
keycode 84 = Last_Console # Alt+SysRq/PrintScrn
#keycode 99 = Control_backslash # SysRq/PrintScrn
keycode 99 = VoidSymbol
control keycode 99 = Control_backslash
plain keycode 70 = Scroll_Lock
shift keycode 70 = Show_Memory
control keycode 70 = Show_State
alt keycode 70 = Show_Registers
keycode 101 = Break # Ctrl+Break/Pause
control keycode 101 = Control_c
shift keycode 101 = Control_backslash
keycode 119 = Pause # Break/Pause
-Andi
next prev parent reply other threads:[~2003-01-11 4:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 9:53 Daniel Ritz
2003-01-10 15:29 ` Hugh Dickins
2003-01-10 16:03 ` William Lee Irwin III
2003-01-10 16:12 ` Andi Kleen
2003-01-10 16:13 ` William Lee Irwin III
2003-01-10 16:34 ` Hugh Dickins
2003-01-10 17:15 ` Robert Love
2003-01-10 19:44 ` Daniel Ritz
2003-01-10 16:37 ` Zwane Mwaikambo
2003-01-10 17:13 ` Valdis.Kletnieks
2003-01-10 17:19 ` Andi Kleen
2003-01-10 19:01 ` Randy.Dunlap
2003-01-11 4:28 ` Andi Kleen [this message]
2003-01-11 4:14 Albert D. Cahalan
2003-01-11 5:33 ` William Lee Irwin III
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=20030111042818.GB10699@wotan.suse.de \
--to=ak@suse.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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
all inboxes | Powered by JetHome®