Thread (29 messages) 29 messages, 6 authors, 2021-12-09

Re: [PATCH v10 08/10] dyndbg: add print-to-tracefs, selftest with it - RFC

From: Steven Rostedt <rostedt@goodmis.org>
Date: 2021-11-12 17:54:58
Also in: amd-gfx, dri-devel, intel-gfx, linux-arm-msm, lkml

On Fri, 12 Nov 2021 12:32:23 -0500
Jason Baron [off-list ref] wrote:
Ok, it looks like Vincent's patch defines a dyndbg event and then uses
'trace_dyndbg()' to output to the 'main' log. So all dynamic output to
the 'main' ftrace buffer goes through that event if I understand it
correctly. Here's a pointer to it for reference:

https://lore.kernel.org/lkml/20200825153338.17061-3-vincent.whitchurch@axis.com/ (local)

Would you be ok with that approach?
Yes that approach is fine, because it doesn't actually go to the main log
unless you enable the dyndbg trace event in the main buffer. You could
also enable that event in an instance and have it go there.

-- Steve

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help