linux-toradex.git/kernel/printk.c, branch tegra-10.9.7

kernel: printk: Add non exported function for clearing the log ring buffer

2010-02-08T23:36:03+00:00

Signed-off-by: San Mehat

printk: Fix log_buf_copy termination.

2010-02-08T23:35:53+00:00

If idx was non-zero and the log had wrapped, len did not get truncated
to stop at the last byte written to the log.

Revert "printk: remove unused code from kernel/printk.c"

2010-02-08T23:35:53+00:00

This reverts commit acff181d3574244e651913df77332e897b88bff4.

ARM: Make low-level printk work

2010-02-04T04:48:10+00:00

Makes low-level printk work.

Signed-off-by: Tony Lindgren

printk: add printk_delay to make messages readable for some scenarios

2009-09-23T14:39:28+00:00

When syslog is not possible, at the same time there's no serial/net
console available, it will be hard to read the printk messages.  For
example oops/panic/warning messages in shutdown phase.

Add a printk delay feature, we can make each printk message delay some
milliseconds.

Setting the delay by proc/sysctl interface: /proc/sys/kernel/printk_delay

The value range from 0 - 10000, default value is 0

[akpm@linux-foundation.org: fix a few things]
Signed-off-by: Dave Young 
Acked-by: Ingo Molnar 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

printk boot_delay: rename printk_delay_msec to loops_per_msec

2009-09-23T14:39:28+00:00

Rename `printk_delay_msec' to `loops_per_msec', because the patch "printk:
add printk_delay to make messages readable for some scenarios" wishes to
more appropriately use the `printk_delay_msec' identifier.

[akpm@linux-foundation.org: add a comment]
Signed-off-by: Dave Young 
Acked-by: Ingo Molnar 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

cleanup console_print()

2009-09-15T00:41:42+00:00

console_print() is an old legacy interface mostly unused in the entire
kernel tree. It's best to clean up its existing use and let developers
use their own implementation of it as they feel fit.

Signed-off-by: Anirban Sinha 
Signed-off-by: Linus Torvalds

printk: Fix "printk: Enable the use of more than one CON_BOOT (early console)"

2009-08-08T16:27:37+00:00

Don't return when we find the first bootconsole - it can leave
other bootconsoles still installed, and they can be used and
cause problems later (if they are in the init section, and
eventually released), and cause problems.  Make sure we remove
all of them.

Signed-off-by: Sonic Zhang 
Signed-off-by: Robin Getz 
Signed-off-by: Andrew Morton 
Signed-off-by: Ingo Molnar

printk: Restore previous console_loglevel when re-enabling logging

2009-07-10T14:02:23+00:00

When logging to console is disabled from userspace using klogctl()
and later re-enabled, console_loglevel gets set to the default
log level instead to the previous value.

This means that if the kernel was booted with 'quiet', the boot is
suddenly no longer quiet after logging to console gets re-enabled.

Save the current console_loglevel when logging is disabled and
restore to that value. If the log level is set to a specific value
while disabled, this is interpreted as an implicit re-enabling of
the logging.

The problem that prompted this patch is described in:

    http://lkml.org/lkml/2009/6/28/234

There are two variations possible on the patch below:

 1) If klogctl(7) is called while logging is not disabled, then set level
    to default (partially preserving current functionality):
  	case 7:		/* Enable logging to console */
 -		console_loglevel = default_console_loglevel;
 +		if (saved_console_loglevel == -1)
 +			console_loglevel = default_console_loglevel;
 +		else {
 +			console_loglevel = saved_console_loglevel;
 +			saved_console_loglevel = -1;
 +		}

 2) If klogctl(8) is called while logging is disabled, then don't enable
    logging, but remember the requested value for when logging does get
    enabled again:
  	case 8:		/* Set level of messages printed to console */
 [...]
 - 		console_loglevel = len;
 +		if (saved_console_loglevel == -1)
 +			console_loglevel = len;
 +		else
 +			saved_console_loglevel = len;

Yet another option would be to ignore the request.

Signed-off-by: Frans Pop 
Cc: cryptsetup@packages.debian.org
Cc: Andrew Morton 
Cc: Linus Torvalds 
LKML-Reference: <200907061331.49930.elendil@planet.nl>
Signed-off-by: Ingo Molnar

printk: Ensure that "console enabled" messages are printed on the console

2009-07-10T10:24:47+00:00

Today, when a console is registered without CON_PRINTBUFFER,
end users never see the announcement of it being added, and
never know if they missed something, if the console is really
at the start or not, and just leads to general confusion.

This re-orders existing code, to make sure the console is
added, before the "console [%s%d] enabled" is printed out -
ensuring that this message is _always_ seen.

This has the desired/intended side effect of making sure that
"console enabled:" messages are printed on the bootconsole, and
the real console. This does cause the same line is printed
twice if the bootconsole and real console are the same device,
but if they are on different devices, the message is printed to
both consoles.

Signed-off-by : Robin Getz 
Cc: "Andrew Morton" 
Cc: "Linus Torvalds" 
LKML-Reference: <200907091308.37370.rgetz@blackfin.uclinux.org>
Signed-off-by: Ingo Molnar