[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200713022356.GB491026@jagdpanzerIV.localdomain>
Date: Mon, 13 Jul 2020 11:23:56 +0900
From: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To: Petr Mladek <pmladek@...e.com>
Cc: John Ogness <john.ogness@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrea Parri <parri.andrea@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Paul McKenney <paulmck@...nel.org>, kexec@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 0/4] printk: replace ringbuffer
On (20/07/10 10:28), Petr Mladek wrote:
> On Thu 2020-07-09 15:29:40, John Ogness wrote:
> > Hello,
> >
> > Here is a v5 for the first series to rework the printk
> > subsystem. The v4 is here [0]. This first series
> > only replaces the existing ringbuffer implementation. No locking
> > is removed. The semantics/behavior of printk are kept the same
> > except for a minor optimization that is reverted (patch 3).
> >
> > John Ogness (4):
> > crash: add VMCOREINFO macro to define offset in a struct declared by
> > typedef
> > printk: add lockless ringbuffer
> > Revert "printk: lock/unlock console only for new logbuf entries"
> > printk: use the lockless ringbuffer
>
> The patchset is committed in printk/linux.git, branch printk-rework.
FWIW,
Acked-by: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Thank you.
-ss
Powered by blists - more mailing lists