diff options
| author | Feng Tang <feng.tang@intel.com> | 2011-03-22 16:34:21 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2011-03-22 17:44:12 -0700 |
| commit | fe3d8ad31cf51b062bbb8a9609eeb1d0c41a7f30 (patch) | |
| tree | f0e0f85582a695d0da7bae97897835ee51a0ab09 /kernel/futex_compat.c | |
| parent | 7bf693951a8e5f7e600a45b74d91d962a453146e (diff) | |
| download | lwn-fe3d8ad31cf51b062bbb8a9609eeb1d0c41a7f30.tar.gz lwn-fe3d8ad31cf51b062bbb8a9609eeb1d0c41a7f30.zip | |
console: prevent registered consoles from dumping old kernel message over again
For a platform with many consoles like:
"console=tty1 console=ttyMFD2 console=ttyS0 earlyprintk=mrst"
Each time when the non "selected_console" (tty1 and ttyMFD2 here) get
registered, the existing kernel message will be printed out on registered
consoles again, the "mrst" early console will get some same message for 3
times, and "tty1" will get some for twice.
As suggested by Andrew Morton, every time a new console is registered, it
will be set as the "exclusive" console which will dump the already
existing kernel messages.
Signed-off-by: Feng Tang <feng.tang@intel.com>
Cc: Greg KH <gregkh@suse.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'kernel/futex_compat.c')
0 files changed, 0 insertions, 0 deletions