On Fri, 2007-09-21 at 17:34 -0400, Kyle Moffett wrote:
quoted text
> With a bit more glue that would cause GCC to notice that for a given  
> qprintk_kmalloc the "qpk->type" is always zero because the level is  
> too high, and therefore it would optimize out *ALL* of the  
> _qprintk_kmalloc(), _qprintk(), and _qprintk_finish() calls.

A negative is that lockup conditions swallow partial messages.

Another approach that doesn't require any new buffering is:

id = printk_block_start();
printk_block(id, fmt, ...)
printk_block_end(id)

and have print_block output the id when multiple IDs are
concurrently issued.

This requires a trivial tool to post-process the log
when messages are interleaved.

-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/