Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759359AbdDSDMk (ORCPT ); Tue, 18 Apr 2017 23:12:40 -0400 Received: from mail-pf0-f194.google.com ([209.85.192.194]:34455 "EHLO mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759303AbdDSDMe (ORCPT ); Tue, 18 Apr 2017 23:12:34 -0400 Subject: Re: [PATCH] of: introduce event tracepoints for dynamic device_node lifecyle To: Steven Rostedt References: <1492475525-10827-1-git-send-email-tyreld@linux.vnet.ibm.com> <58F6AA35.2040902@gmail.com> <20170418224657.1b7ed057@grimm.local.home> Cc: Tyrel Datwyler , 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 From: Frank Rowand Message-ID: <58F6D588.2050402@gmail.com> Date: Tue, 18 Apr 2017 20:12:08 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <20170418224657.1b7ed057@grimm.local.home> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 853 Lines: 29 On 04/18/17 19:46, Steven Rostedt wrote: > On Tue, 18 Apr 2017 17:07:17 -0700 > Frank Rowand 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. >> > . >