diff options
author | Sergey Senozhatsky <[email protected]> | 2018-04-19 10:42:50 +0900 |
---|---|---|
committer | Petr Mladek <[email protected]> | 2018-04-25 13:26:02 +0200 |
commit | 43a17111c2553925f65e7be9b9c3f9d90cf29a8b (patch) | |
tree | 3e14a2ad36779608bc6d4d3bfbdb12ef6c5482d2 /tools/perf/scripts/python/event_analyzing_sample.py | |
parent | 357aa6aefebe888c712152cb83c9e700f98eebd1 (diff) |
printk: wake up klogd in vprintk_emit
We wake up klogd very late - only when current console_sem owner
is done pushing pending kernel messages to the serial/net consoles.
In some cases this results in lost syslog messages, because kernel
log buffer is a circular buffer and if we don't wakeup syslog long
enough there are chances that logbuf simply will wrap around.
The patch moves the klogd wake up call to vprintk_emit(), which is
the only legit way for a kernel message to appear in the logbuf,
right after the attempt to handle consoles. As a result, klogd
will get waken either after flushing the new message to consoles
or immediately when consoles are still busy with older messages.
Link: http://lkml.kernel.org/r/[email protected]
To: Steven Rostedt <[email protected]>
Cc: Andrew Morton <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Tejun Heo <[email protected]>
Cc: [email protected]
Signed-off-by: Sergey Senozhatsky <[email protected]>
Signed-off-by: Petr Mladek <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions