All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: 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, mpe@ellerman.id.au, mingo@redhat.com
Subject: Re: [PATCH] of: introduce event tracepoints for dynamic device_node lifecyle
Date: Tue, 18 Apr 2017 20:12:08 -0700	[thread overview]
Message-ID: <58F6D588.2050402@gmail.com> (raw)
In-Reply-To: <20170418224657.1b7ed057@grimm.local.home>

On 04/18/17 19:46, Steven Rostedt wrote:
> On Tue, 18 Apr 2017 17:07:17 -0700
> Frank Rowand <frowand.list@gmail.com> wrote:
> 
> 
>> As far as I know, there is no easy way to combine trace data and printk()
>> style data to create a single chronology of events.  If some of the
>> information needed to debug an issue is trace data and some is printk()
>> style data then it becomes more difficult to understand the overall
>> situation.
> 
> You mean like:
> 
>  # echo 1 > /sys/kernel/debug/tracing/events/printk/console/enable
> 
> Makes all printks also go into the ftrace ring buffer.

Thanks!  I was hoping there was going to be an easy answer like this.


> -- Steve
> 
>>
>> If Rob wants to convert printk() style data to trace data (and I can't
>> convince him otherwise) then I will have further comments on this specific
>> patch.
>>
> .
> 

WARNING: multiple messages have this Message-ID (diff)
From: Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Steven Rostedt <rostedt-nx8X9YLhiw1AfugRpC6u6w@public.gmane.org>
Cc: Tyrel Datwyler
	<tyreld-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
	robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	nfont-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org,
	mpe-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org,
	mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH] of: introduce event tracepoints for dynamic device_node lifecyle
Date: Tue, 18 Apr 2017 20:12:08 -0700	[thread overview]
Message-ID: <58F6D588.2050402@gmail.com> (raw)
In-Reply-To: <20170418224657.1b7ed057-2kNGR76GQU9OHLTnHDQRgA@public.gmane.org>

On 04/18/17 19:46, Steven Rostedt wrote:
> On Tue, 18 Apr 2017 17:07:17 -0700
> Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> 
> 
>> As far as I know, there is no easy way to combine trace data and printk()
>> style data to create a single chronology of events.  If some of the
>> information needed to debug an issue is trace data and some is printk()
>> style data then it becomes more difficult to understand the overall
>> situation.
> 
> You mean like:
> 
>  # echo 1 > /sys/kernel/debug/tracing/events/printk/console/enable
> 
> Makes all printks also go into the ftrace ring buffer.

Thanks!  I was hoping there was going to be an easy answer like this.


> -- Steve
> 
>>
>> If Rob wants to convert printk() style data to trace data (and I can't
>> convince him otherwise) then I will have further comments on this specific
>> patch.
>>
> .
> 

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-04-19  3:12 UTC|newest]

Thread overview: 51+ 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:32 ` Tyrel Datwyler
2017-04-18  0:35 ` Tyrel Datwyler
2017-04-18  0:35   ` Tyrel Datwyler
2017-04-18 16:46 ` Rob Herring
2017-04-18 16:46   ` Rob Herring
2017-04-19  2:30   ` Oliver O'Halloran
2017-04-19  2:30     ` Oliver O'Halloran
2017-04-19 10:13     ` Michael Ellerman
2017-04-19 10:13       ` Michael Ellerman
2017-04-19 21:13       ` Tyrel Datwyler
2017-04-19  0:07 ` Frank Rowand
2017-04-19  0:07   ` Frank Rowand
2017-04-19  1:31   ` Michael Ellerman
2017-04-19  1:31     ` Michael Ellerman
2017-04-19  2:31     ` Frank Rowand
2017-04-19  2:31       ` Frank Rowand
2017-04-19 18:33       ` Tyrel Datwyler
2017-04-19 18:33         ` Tyrel Datwyler
2017-04-19 23:27     ` Tyrel Datwyler
2017-04-19 23:27       ` Tyrel Datwyler
2017-04-20  2:33       ` Steven Rostedt
2017-04-20  2:33         ` Steven Rostedt
2017-04-20  4:47         ` Frank Rowand
2017-04-20  4:47           ` Frank Rowand
2017-04-20  5:24         ` Tyrel Datwyler
2017-04-20  5:24           ` Tyrel Datwyler
2017-04-20 13:37           ` Steven Rostedt
2017-04-20 13:37             ` Steven Rostedt
2017-04-20  4:43       ` Frank Rowand
2017-04-20  5:13         ` Frank Rowand
2017-04-20  5:13           ` Frank Rowand
2017-04-20 16:51         ` Tyrel Datwyler
2017-04-20 16:51           ` Tyrel Datwyler
2017-04-20 19:34           ` Frank Rowand
2017-04-20 19:34             ` Frank Rowand
2017-04-21  1:57             ` Michael Ellerman
2017-04-19  1:42   ` Frank Rowand
2017-04-19  1:42     ` Frank Rowand
2017-04-19  2:49     ` Steven Rostedt
2017-04-19 18:45       ` Tyrel Datwyler
2017-04-19 18:45         ` Tyrel Datwyler
2017-04-20  2:37         ` Frank Rowand
2017-04-20  2:37           ` Frank Rowand
2017-04-20 10:44           ` Frank Rowand
2017-04-20 10:44             ` Frank Rowand
2017-04-19  2:46   ` Steven Rostedt
2017-04-19  3:12     ` Frank Rowand [this message]
2017-04-19  3:12       ` Frank Rowand
2017-04-19 17:44 ` 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=58F6D588.2050402@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.