On Wed, 19 Apr 2017 22:24:58 -0700 Tyrel Datwyler <turtle.in.the.kernel@xxxxxxxxx> wrote: > On 04/19/2017 07:33 PM, Steven Rostedt wrote: > > On Wed, 19 Apr 2017 16:27:10 -0700 > > Tyrel Datwyler <turtle.in.the.kernel@xxxxxxxxx> wrote: > > > >> # 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 -- 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
