[lkml]   [2017]   [Oct]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] printk: Remove superfluous memory barriers from printk_safe
On Wed 2017-10-11 12:46:47, Steven Rostedt wrote:
> From: Steven Rostedt (VMware) <>
> The variable printk_safe_irq_ready is set and never cleared at system
> boot up, when there's only one CPU active. It is set before other
> CPUs come on line. Also, it is extremely unlikely that an NMI would
> trigger this early in boot up (which I wonder why we even have this
> variable at all).
> Also mark the printk_safe_irq_ready as read mostly, as it is set at
> system boot up, and never touched again.
> Signed-off-by: Steven Rostedt (VMware) <>

Great catch! It makes perfect sense:

Reviewed-by: Petr Mladek <>

Best Regards,

 \ /
  Last update: 2017-10-12 11:35    [W:0.042 / U:0.988 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site