Re: [RFC 2/2] printk: Add more information about the printk caller

[John Ogness <john.ogness@linutronix.de>]

On 2020-09-24, Sergey Senozhatsky <sergey.senozhatsky@gmail.com> wrote:
> A question. Suppose we have a task which does
>
> 	CPU0
>
> 	pr_err(...);
>
> 	preempt_disable();
> 	pr_err(...);
> 	preempt_enable();
>
> 	pr_err(...);
>
> 	rcu_read_lock();
> 	pr_info(...);
> 	rcu_read_unlock();
>
> Should we distinguish those as 3 different contexts?
>
> - normal printk
> - printk under disabled preemption (affects scheduling)
> - printk under RCU read side lock (affects RCU grace periods)

The internal purpose of the printk_info's @caller_id is to support
_some_ sanity with LOG_CONT. True LOG_CONT sanity will not be available
until we provide a context API like we previously talked about [0]. But
for now it is good enough (even if it is not good).

We can also store various flags and counters to describe the current
context. But these would only exist to provide the user with information
rather than because printk itself needs it. I only mention this so that
we don't get things mixed up. We can add as much information as want,
but LOG_CONT will only be interested in a subset of that.

John Ogness