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

From: Petr Mladek
Date: Wed Dec 09 2020 - 06:16:00 EST

Next message: kernel test robot: "drivers/staging/media/atomisp//pci/ia_css_firmware.h:52:29: warning: declaration of 'struct device' will not be visible outside of this function"
Previous message: Enrico Weigelt, metux IT consult: "Re: [PATCH] drivers: usb: gadget: prefer pr_*() functions over raw printk()"
In reply to: John Ogness: "[PATCH next v4 1/2] printk: inline log_output(),log_store() in vprintk_store()"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed 2020-12-09 01:50:51, John Ogness wrote:
> 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.

Both patches are pushed in printk/linux.git, branch printk-rework.

I hurried so that we could get some testing linux-next before
the merge window opens.

We are going to see if the many barriers in the ring buffer
code are enough ;-) I keep my fingers crossed.

Best Regards,
Petr

Next message: kernel test robot: "drivers/staging/media/atomisp//pci/ia_css_firmware.h:52:29: warning: declaration of 'struct device' will not be visible outside of this function"
Previous message: Enrico Weigelt, metux IT consult: "Re: [PATCH] drivers: usb: gadget: prefer pr_*() functions over raw printk()"
In reply to: John Ogness: "[PATCH next v4 1/2] printk: inline log_output(),log_store() in vprintk_store()"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]