[PATCH v3 0/2] printk: console: Per-console loglevels

Chris Down posted 2 patches 3 years, 9 months ago
There is a newer version of this series
Documentation/ABI/testing/sysfs-class-console |  43 +++
.../admin-guide/kernel-parameters.txt         |  28 +-
.../admin-guide/per-console-loglevel.rst      |  92 ++++++
Documentation/admin-guide/serial-console.rst  |  17 +-
Documentation/core-api/printk-basics.rst      |  35 +-
Documentation/networking/netconsole.rst       |  17 +
MAINTAINERS                                   |   3 +
include/linux/console.h                       |  24 ++
kernel/printk/console_cmdline.h               |   2 +
kernel/printk/printk.c                        | 311 +++++++++++++++++-
kernel/printk/sysctl.c                        |  64 +++-
11 files changed, 599 insertions(+), 37 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-class-console
create mode 100644 Documentation/admin-guide/per-console-loglevel.rst
[PATCH v3 0/2] printk: console: Per-console loglevels
Posted by Chris Down 3 years, 9 months ago
v3:

- Update to work with John's kthread patches
- Remove force_console_loglevel, now we only have global and local levels
- Remove minimum_console_loglevel control and document how to change it
- The minimum loglevel is now only honoured on setting global/local level
- Add ignore_per_console_loglevel
- Return -EINVAL if trying to set below minimum console level
- Add parser for named console= options
- Fix docs around ignore_loglevel: it can be changed at runtime
- Fix ordering in "in order of authority" docs
- Remove duplicated default_console_loglevel doc
- Only warn once on syslog() use

v2:

- Dynamically allocate struct device*
- Document sysfs attributes in Documentation/ABI/
- Use sysfs_emit() instead of sprintf() in dev sysfs files
- Remove WARN_ON() for device_add/IS_ERR(console_class)
- Remove "soon" comment for kernel.printk
- Fix !CONFIG_PRINTK build
- Fix device_unregister() NULL dereference if called before class setup
- Add new documentation to MAINTAINERS

Chris Down (2):
  printk: console: Create console= parser that supports named options
  printk: console: Support console-specific loglevels

 Documentation/ABI/testing/sysfs-class-console |  43 +++
 .../admin-guide/kernel-parameters.txt         |  28 +-
 .../admin-guide/per-console-loglevel.rst      |  92 ++++++
 Documentation/admin-guide/serial-console.rst  |  17 +-
 Documentation/core-api/printk-basics.rst      |  35 +-
 Documentation/networking/netconsole.rst       |  17 +
 MAINTAINERS                                   |   3 +
 include/linux/console.h                       |  24 ++
 kernel/printk/console_cmdline.h               |   2 +
 kernel/printk/printk.c                        | 311 +++++++++++++++++-
 kernel/printk/sysctl.c                        |  64 +++-
 11 files changed, 599 insertions(+), 37 deletions(-)
 create mode 100644 Documentation/ABI/testing/sysfs-class-console
 create mode 100644 Documentation/admin-guide/per-console-loglevel.rst


base-commit: 9d882352bac8f2ff3753d691e2dc65fcaf738729
-- 
2.37.1
Re: [PATCH v3 0/2] printk: console: Per-console loglevels
Posted by John Ogness 3 years, 9 months ago
On 2022-07-20, Chris Down <chris@chrisdown.name> wrote:
> v3:
>
> - Update to work with John's kthread patches

This will get a bit tricky, since I am also preparing a new kthread
series. But for now it is helpful to base your work on the previous
kthread work.

Thanks for your efforts on this!

John
Re: [PATCH v3 0/2] printk: console: Per-console loglevels
Posted by Chris Down 3 years, 9 months ago
John Ogness writes:
>On 2022-07-20, Chris Down <chris@chrisdown.name> wrote:
>> v3:
>>
>> - Update to work with John's kthread patches
>
>This will get a bit tricky, since I am also preparing a new kthread
>series. But for now it is helpful to base your work on the previous
>kthread work.

No worries -- I don't think it should get too bad. If I recall correctly, the 
only real changes were around handling suppress_message_printing in the new 
model, and they were fairly minor.

>Thanks for your efforts on this!

Likewise on the kthread work! Just let me know if/when you want me to rebase. 
:-)