[lkml]   [2019]   [Aug]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[RFC PATCH v4 0/9] printk: new ringbuffer implementation

This is a follow-up RFC on the work to re-implement much of
the core of printk. The threads for the previous RFC versions
are here: v1[0], v2[1], v3[2].

This series only builds upon v3 (i.e. the first part of this
series is exactly v3). The main purpose of this series is to
replace the current printk ringbuffer with the new
ringbuffer. As was discussed[3], this is a conservative
first step to rework printk. For example, all logbuf_lock
usage is kept even though the new ringbuffer does not
require it. This avoids any side-effect bugs in case the
logbuf_lock is (unintentionally) synchronizing more than
just the ringbuffer. However, this also means that the
series does not bring any improvements, just swapping out
implementations. A future patch will remove the logbuf_lock.

Except for the test module (patches 2 and 6), the rest may
already be interesting for mainline as is. I have tested
the various interfaces (console, /dev/kmsg, syslog,
kmsg_dump) and their features and all looks good AFAICT.

The patches can be broken down as follows:

1-2: the previously posted RFCv3

3-7: addresses minor issues from RFCv3

8: adds new high-level ringbuffer functions to support
printk (nothing involving new memory barriers)

9: replace the ringbuffer usage in printk.c

One important thing to know (as is mentioned in the commit
message of patch 9), there are 2 externally visible

- vmcore info changes

- powerpc powernv/opal memdump of log discontinued

I have no idea how acceptable these changes are.

I will not be posting any further printk patches until I
have received some feedback on this. I appreciate all the
help so far. I realize that this is a lot of code to go

The series is based on 5.3-rc3. I would encourage people to
apply the series and give it a run. I expect that you
will not notice any difference with your printk behaviour.

John Ogness


John Ogness (9):
printk-rb: add a new printk ringbuffer implementation
printk-rb: add test module
printk-rb: fix missing includes/exports
printk-rb: initialize new descriptors as invalid
printk-rb: remove extra data buffer size allocation
printk-rb: adjust test module ringbuffer sizes
printk-rb: increase size of seq and size variables
printk-rb: new functionality to support printk
printk: use a new ringbuffer implementation

arch/powerpc/platforms/powernv/opal.c | 22 +-
include/linux/kmsg_dump.h | 6 +-
include/linux/printk.h | 12 -
kernel/printk/Makefile | 5 +
kernel/printk/dataring.c | 809 ++++++++++++++++++
kernel/printk/dataring.h | 108 +++
kernel/printk/numlist.c | 376 +++++++++
kernel/printk/numlist.h | 72 ++
kernel/printk/printk.c | 745 +++++++++--------
kernel/printk/ringbuffer.c | 1079 +++++++++++++++++++++++++
kernel/printk/ringbuffer.h | 354 ++++++++
kernel/printk/test_prb.c | 256 ++++++
12 files changed, 3450 insertions(+), 394 deletions(-)
create mode 100644 kernel/printk/dataring.c
create mode 100644 kernel/printk/dataring.h
create mode 100644 kernel/printk/numlist.c
create mode 100644 kernel/printk/numlist.h
create mode 100644 kernel/printk/ringbuffer.c
create mode 100644 kernel/printk/ringbuffer.h
create mode 100644 kernel/printk/test_prb.c


 \ /
  Last update: 2019-08-08 00:27    [W:0.378 / U:5.524 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site