Re: [PATCH 3/6] tracing: Add tp_pstore cmdline to have tracepoints go to pstore

2018-10-10 Thread Steven Rostedt
On Tue, 9 Oct 2018 23:52:14 +0530 Sai Prakash Ranjan wrote: > >>> Also regarding the warning on "event_call->event.funcs->trace()" call, > >>> I see it everytime without spinlock. Also we see output_printk using > >>> spinlock when making this call. I could not find a way to pass event > >>>

Re: [PATCH 3/6] tracing: Add tp_pstore cmdline to have tracepoints go to pstore

2018-10-10 Thread Steven Rostedt
On Tue, 9 Oct 2018 23:52:14 +0530 Sai Prakash Ranjan wrote: > >>> Also regarding the warning on "event_call->event.funcs->trace()" call, > >>> I see it everytime without spinlock. Also we see output_printk using > >>> spinlock when making this call. I could not find a way to pass event > >>>

Re: [PATCH 3/6] tracing: Add tp_pstore cmdline to have tracepoints go to pstore

2018-10-09 Thread Sai Prakash Ranjan
On 10/9/2018 4:10 AM, Joel Fernandes wrote: On Mon, Oct 08, 2018 at 10:36:59AM -0400, Steven Rostedt wrote: On Mon, 8 Oct 2018 19:46:15 +0530 Sai Prakash Ranjan wrote: Hi Joel, Sorry for the long delay in updating this thread. But I just observed one weird behaviour in ftrace-ramoops when I

Re: [PATCH 3/6] tracing: Add tp_pstore cmdline to have tracepoints go to pstore

2018-10-09 Thread Sai Prakash Ranjan
On 10/9/2018 4:10 AM, Joel Fernandes wrote: On Mon, Oct 08, 2018 at 10:36:59AM -0400, Steven Rostedt wrote: On Mon, 8 Oct 2018 19:46:15 +0530 Sai Prakash Ranjan wrote: Hi Joel, Sorry for the long delay in updating this thread. But I just observed one weird behaviour in ftrace-ramoops when I

Re: [PATCH 3/6] tracing: Add tp_pstore cmdline to have tracepoints go to pstore

2018-10-08 Thread Joel Fernandes
On Mon, Oct 08, 2018 at 10:36:59AM -0400, Steven Rostedt wrote: > On Mon, 8 Oct 2018 19:46:15 +0530 > Sai Prakash Ranjan wrote: > > > Hi Joel, > > > > Sorry for the long delay in updating this thread. > > But I just observed one weird behaviour in ftrace-ramoops when I was > > trying to use

Re: [PATCH 3/6] tracing: Add tp_pstore cmdline to have tracepoints go to pstore

2018-10-08 Thread Joel Fernandes
On Mon, Oct 08, 2018 at 10:36:59AM -0400, Steven Rostedt wrote: > On Mon, 8 Oct 2018 19:46:15 +0530 > Sai Prakash Ranjan wrote: > > > Hi Joel, > > > > Sorry for the long delay in updating this thread. > > But I just observed one weird behaviour in ftrace-ramoops when I was > > trying to use

Re: [PATCH 3/6] tracing: Add tp_pstore cmdline to have tracepoints go to pstore

2018-10-08 Thread Steven Rostedt
On Mon, 8 Oct 2018 19:46:15 +0530 Sai Prakash Ranjan wrote: > Hi Joel, > > Sorry for the long delay in updating this thread. > But I just observed one weird behaviour in ftrace-ramoops when I was > trying to use binary record instead of rendering text for event-ramoops. > > Even though we set

Re: [PATCH 3/6] tracing: Add tp_pstore cmdline to have tracepoints go to pstore

2018-10-08 Thread Steven Rostedt
On Mon, 8 Oct 2018 19:46:15 +0530 Sai Prakash Ranjan wrote: > Hi Joel, > > Sorry for the long delay in updating this thread. > But I just observed one weird behaviour in ftrace-ramoops when I was > trying to use binary record instead of rendering text for event-ramoops. > > Even though we set

Re: [PATCH 3/6] tracing: Add tp_pstore cmdline to have tracepoints go to pstore

2018-10-08 Thread Sai Prakash Ranjan
On 9/26/2018 3:16 PM, Sai Prakash Ranjan wrote: On 9/26/2018 2:55 AM, Joel Fernandes wrote: On Sat, Sep 8, 2018 at 1:28 PM Sai Prakash Ranjan wrote: Add the kernel command line tp_pstore option that will have tracepoints go to persistent ram buffer as well as to the trace buffer for further

Re: [PATCH 3/6] tracing: Add tp_pstore cmdline to have tracepoints go to pstore

2018-10-08 Thread Sai Prakash Ranjan
On 9/26/2018 3:16 PM, Sai Prakash Ranjan wrote: On 9/26/2018 2:55 AM, Joel Fernandes wrote: On Sat, Sep 8, 2018 at 1:28 PM Sai Prakash Ranjan wrote: Add the kernel command line tp_pstore option that will have tracepoints go to persistent ram buffer as well as to the trace buffer for further

Re: [PATCH 3/6] tracing: Add tp_pstore cmdline to have tracepoints go to pstore

2018-09-26 Thread Sai Prakash Ranjan
On 9/26/2018 2:55 AM, Joel Fernandes wrote: On Sat, Sep 8, 2018 at 1:28 PM Sai Prakash Ranjan wrote: Add the kernel command line tp_pstore option that will have tracepoints go to persistent ram buffer as well as to the trace buffer for further debugging. This is similar to tp_printk cmdline

Re: [PATCH 3/6] tracing: Add tp_pstore cmdline to have tracepoints go to pstore

2018-09-26 Thread Sai Prakash Ranjan
On 9/26/2018 2:55 AM, Joel Fernandes wrote: On Sat, Sep 8, 2018 at 1:28 PM Sai Prakash Ranjan wrote: Add the kernel command line tp_pstore option that will have tracepoints go to persistent ram buffer as well as to the trace buffer for further debugging. This is similar to tp_printk cmdline

Re: [PATCH 3/6] tracing: Add tp_pstore cmdline to have tracepoints go to pstore

2018-09-25 Thread Joel Fernandes
On Sat, Sep 8, 2018 at 1:28 PM Sai Prakash Ranjan wrote: > > Add the kernel command line tp_pstore option that will have > tracepoints go to persistent ram buffer as well as to the > trace buffer for further debugging. This is similar to tp_printk > cmdline option of ftrace. > > Pstore support

Re: [PATCH 3/6] tracing: Add tp_pstore cmdline to have tracepoints go to pstore

2018-09-25 Thread Joel Fernandes
On Sat, Sep 8, 2018 at 1:28 PM Sai Prakash Ranjan wrote: > > Add the kernel command line tp_pstore option that will have > tracepoints go to persistent ram buffer as well as to the > trace buffer for further debugging. This is similar to tp_printk > cmdline option of ftrace. > > Pstore support

[PATCH 3/6] tracing: Add tp_pstore cmdline to have tracepoints go to pstore

2018-09-08 Thread Sai Prakash Ranjan
Add the kernel command line tp_pstore option that will have tracepoints go to persistent ram buffer as well as to the trace buffer for further debugging. This is similar to tp_printk cmdline option of ftrace. Pstore support for event tracing is already added and we enable logging to pstore only

[PATCH 3/6] tracing: Add tp_pstore cmdline to have tracepoints go to pstore

2018-09-08 Thread Sai Prakash Ranjan
Add the kernel command line tp_pstore option that will have tracepoints go to persistent ram buffer as well as to the trace buffer for further debugging. This is similar to tp_printk cmdline option of ftrace. Pstore support for event tracing is already added and we enable logging to pstore only