Re: [RFC][PATCHv3 1/5] printk: move printk_pending out of per-cpu

2017-05-25 Thread Petr Mladek
On Thu 2017-05-25 21:36:33, Sergey Senozhatsky wrote: > On (05/25/17 14:11), Petr Mladek wrote: > [..] > > The variable is used only when CONFIG_PRINTK is defined at > > the moment, so this produces a warning about an unused variable. > > > > interesting... `printk_pending' is used in console_unl

Re: [RFC][PATCHv3 1/5] printk: move printk_pending out of per-cpu

2017-05-25 Thread Sergey Senozhatsky
On (05/25/17 14:11), Petr Mladek wrote: [..] > The variable is used only when CONFIG_PRINTK is defined at > the moment, so this produces a warning about an unused variable. > interesting... `printk_pending' is used in console_unlock(), which is always available. -ss

Re: [RFC][PATCHv3 1/5] printk: move printk_pending out of per-cpu

2017-05-25 Thread Petr Mladek
On Tue 2017-05-09 17:28:55, Sergey Senozhatsky wrote: > Do not keep `printk_pending' in per-CPU area. We set the following bits > of printk_pending: > a) PRINTK_PENDING_WAKEUP > when we need to wakeup klogd > b) PRINTK_PENDING_OUTPUT > when there is a pending output from deferred printk

[RFC][PATCHv3 1/5] printk: move printk_pending out of per-cpu

2017-05-09 Thread Sergey Senozhatsky
Do not keep `printk_pending' in per-CPU area. We set the following bits of printk_pending: a) PRINTK_PENDING_WAKEUP when we need to wakeup klogd b) PRINTK_PENDING_OUTPUT when there is a pending output from deferred printk and we need to call console_unlock(). So none of the