[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170420093704.577f262d@gandalf.local.home>
Date: Thu, 20 Apr 2017 09:37:04 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Tyrel Datwyler <turtle.in.the.kernel@...il.com>
Cc: Michael Ellerman <mpe@...erman.id.au>,
Frank Rowand <frowand.list@...il.com>,
Tyrel Datwyler <tyreld@...ux.vnet.ibm.com>, robh+dt@...nel.org,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, nfont@...ux.vnet.ibm.com,
mingo@...hat.com
Subject: Re: [PATCH] of: introduce event tracepoints for dynamic device_node
lifecyle
On Wed, 19 Apr 2017 22:24:58 -0700
Tyrel Datwyler <turtle.in.the.kernel@...il.com> 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@...il.com> wrote:
> >
> >> # echo stacktrace > /sys/kernel/debug/tracing/trace_options
> >> # cat trace | grep -A6 "/pci@...000020000018"
> >
> > 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
Powered by blists - more mailing lists