[PATCH next v4 0/2] printk: remove logbuf_lock writer-protection of ringbuffer

From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org
Subject: [PATCH next v4 0/2] printk: remove logbuf_lock writer-protection of ringbuffer
Date: Wed,  9 Dec 2020 01:50:51 +0106	[thread overview]
Message-ID: <20201209004453.17720-1-john.ogness@linutronix.de> (raw)

Hello,

Here is a v4 of the series to partially remove logbuf_lock.
v3 is here[0]. This series removes logbuf_lock usage of most
ringbuffer writers. The remaining logbuf_lock users are
using the lock to synchronize other variables. These other
users will be addressed in a later series.

I have tried to keep these changes minimal so that we can feel
comfortable for the upcoming 5.11 merge window.

Although small, this series is significant because it allows
printk callers direct lockless access to the ringbuffer and
it replaces the use of a static sprint buffer with sprint'ing
directly to the reserved ringbuffer data block.

This series is based on next-20201208.

John Ogness

[0] https://lkml.kernel.org/r/20201207222020.2923-1-john.ogness@linutronix.de

John Ogness (2):
  printk: inline log_output(),log_store() in vprintk_store()
  printk: remove logbuf_lock writer-protection of ringbuffer

 kernel/printk/printk.c | 247 ++++++++++++++++++++++++-----------------
 1 file changed, 147 insertions(+), 100 deletions(-)

-- 
2.20.1