Messages in this thread | | | Date | Mon, 4 Mar 2019 12:33:00 +0900 | From | Sergey Senozhatsky <> | Subject | Re: [PATCH] printk/console: Do not suppress information about dropped messages |
| |
On (02/27/19 09:30), Petr Mladek wrote: > Good point! There is a simple fix for this. We could print the warning > also when all messages are proceed and we are about to leave > the for-cycle.
I'd prefer to have lost-messages reporting be less of a summary and more of an "error". I think the sooner we report it the better. I don't think that the time we need to print lost-messages on the consoles is significant enough to worry about it; if call_console_drivers() becomes such a problem that any extra char we print causes message-drop then we can disable printk_time or/and printk caller_id prefix printout (can save us more CPU cycles).
-ss
| |