Thread (105 messages) 105 messages, 18 authors, 2022-07-30

Re: [PATCH 24/36] printk: Remove trace_.*_rcuidle() usage

From: Sergey Senozhatsky <senozhatsky@chromium.org>
Date: 2022-06-11 02:33:29
Also in: linux-acpi, linux-arch, linux-arm-msm, linux-clk, linux-m68k, linux-mips, linux-omap, linux-perf-users, linux-pm, linux-riscv, linux-s390, linux-sh, linux-tegra, linux-um, linuxppc-dev, lkml, rcu, sparclinux, xen-devel

On Thu, Jun 9, 2022 at 10:02 PM Petr Mladek [off-list ref] wrote:
On Thu 2022-06-09 20:30:58, Sergey Senozhatsky wrote:
quoted
My emails are getting rejected... Let me try web-interface
Bad day for mail sending. I have problems as well ;-)
For me the problem is still there and apparently it's an "too many
recipients" error.
quoted
I'm somewhat curious whether we can actually remove that trace event.
Good question.

Well, I think that it might be useful. It allows to see trace and
printk messages together.
Fair enough. Seems that back in 2011 people were pretty happy with it
https://lore.kernel.org/all/1322161388.5366.54.camel@jlt3.sipsolutions.net/T/#m7bf6416f469119372191f22a6ecf653c5f7331d2 (local)

but... reportedly, one of the folks who Ack-ed it (*cough cough*
PeterZ) has never used it.
It was ugly when it was in the console code. The new location
in vprintk_store() allows to have it even "correctly" sorted
(timestamp) against other tracing messages.
That's true.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help