From: Tyrel Datwyler <turtle.in.the.kernel@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Frank Rowand <frowand.list@gmail.com>,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
robh+dt@kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
nfont@linux.vnet.ibm.com, mingo@redhat.com
Subject: Re: [PATCH] of: introduce event tracepoints for dynamic device_node lifecyle
Date: Wed, 19 Apr 2017 22:24:58 -0700 [thread overview]
Message-ID: <90e008a7-0660-99b9-edbe-6bf146268ba8@gmail.com> (raw)
In-Reply-To: <20170419223342.0bbe2593@grimm.local.home>
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@gmail.com> 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.
-Tyrel
>
> # cd /sys/kernel/debug/tracing
> # echo "stacktrace if common_pid == $$ && reason == 3" \
> > events/tlb/tlb_flush/trigger
>
> # cat trace
> bash-1103 [003] ...1 1290.100133: tlb_flush: pages:-1 reason:local mm shootdown (3)
> bash-1103 [003] ...2 1290.100140: <stack trace>
> => copy_process.part.39
> => _do_fork
> => SyS_clone
> => do_syscall_64
> => return_from_SYSCALL_64
>
> -- Steve
>
next prev parent reply other threads:[~2017-04-20 5:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 0:32 [PATCH] of: introduce event tracepoints for dynamic device_node lifecyle Tyrel Datwyler
2017-04-18 0:35 ` Tyrel Datwyler
2017-04-18 16:46 ` Rob Herring
2017-04-19 2:30 ` Oliver O'Halloran
2017-04-19 10:13 ` Michael Ellerman
2017-04-19 21:13 ` Tyrel Datwyler
2017-04-19 0:07 ` Frank Rowand
2017-04-19 1:31 ` Michael Ellerman
2017-04-19 2:31 ` Frank Rowand
2017-04-19 18:33 ` Tyrel Datwyler
2017-04-19 23:27 ` Tyrel Datwyler
2017-04-20 2:33 ` Steven Rostedt
2017-04-20 4:47 ` Frank Rowand
2017-04-20 5:24 ` Tyrel Datwyler [this message]
2017-04-20 13:37 ` Steven Rostedt
2017-04-20 4:43 ` Frank Rowand
2017-04-20 5:13 ` Frank Rowand
2017-04-20 16:51 ` Tyrel Datwyler
2017-04-20 19:34 ` Frank Rowand
2017-04-21 1:57 ` Michael Ellerman
2017-04-19 1:42 ` Frank Rowand
2017-04-19 2:49 ` Steven Rostedt
2017-04-19 18:45 ` Tyrel Datwyler
2017-04-20 2:37 ` Frank Rowand
2017-04-20 10:44 ` Frank Rowand
2017-04-19 2:46 ` Steven Rostedt
2017-04-19 3:12 ` Frank Rowand
2017-04-19 17:44 ` Frank Rowand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=90e008a7-0660-99b9-edbe-6bf146268ba8@gmail.com \
--to=turtle.in.the.kernel@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=nfont@linux.vnet.ibm.com \
--cc=robh+dt@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tyreld@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).