On Wed, 24 Jan 2018 22:55:13 -0800 Frank Rowand <frowand.list@xxxxxxxxx> wrote: > Hi Steve, > > Off the top of your head, can you tell me know early in the boot > process a trace_event can be called and successfully provide the > data to someone trying to debug early boot issues? The trace events are enabled by early_initcall(). > > Also, way back when version 1 of this patch was being discussed, > a question about stacktrace triggers: > > >>> # echo stacktrace > /sys/kernel/debug/tracing/trace_options > >>> # cat trace | grep -A6 "/pci@800000020000018" > >> > >> Just to let you know that there is now stacktrace event triggers, where > >> you don't need to stacktrace all events, you can pick and choose. And > >> even filter the stack trace on specific fields of the event. > > > > This is great, and I did figure that out this afternoon. One thing I was > > still trying to determine though was whether its possible to set these > > triggers at boot? As far as I could tell I'm still limited to > > "trace_options=stacktrace" as a kernel boot parameter to get the stack > > for event tracepoints. > > No not yet. But I'll add that to the todo list. > > Thanks, > > -- Steve > > Is this still on your todo list, or is it now available? Still on the todo list. As someone once said, there really is no todo list, but just work on the stuff that people are yelling the loudest about. Yell louder, and it will get done quicker ;-) -- Steve -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
