On Thu, 23 Jun 2016 10:58:55 -0400 (EDT)
Chunyu Hu wrote:
> Sure, if your time allowing me to send it tomorrow, If not, feel free
> to fix it as your way.
I'll let you do it ;-) (I need minions!)
-- Steve
On Thu, 23 Jun 2016 10:58:55 -0400 (EDT)
Chunyu Hu wrote:
> Sure, if your time allowing me to send it tomorrow, If not, feel free
> to fix it as your way.
I'll let you do it ;-) (I need minions!)
-- Steve
- Original Message -
> From: "Steven Rostedt" <rost...@goodmis.org>
> To: "Chunyu Hu" <ch...@redhat.com>
> Cc: linux-kernel@vger.kernel.org
> Sent: Thursday, June 23, 2016 10:39:20 PM
> Subject: Re: [PATCH] tracing: Fix oops caused by grap
- Original Message -
> From: "Steven Rostedt"
> To: "Chunyu Hu"
> Cc: linux-kernel@vger.kernel.org
> Sent: Thursday, June 23, 2016 10:39:20 PM
> Subject: Re: [PATCH] tracing: Fix oops caused by graph notrace filter
>
> On Thu, 23 Jun 201
On Thu, 23 Jun 2016 10:20:31 -0400 (EDT)
Chunyu Hu wrote:
> I tried the patch, if just for resolving the oops issue, it's indeed enough.
> But if we care about just this filter, and compare this with the
> trace_graph_entry
> filter handling, I found that, the depth 0 item
On Thu, 23 Jun 2016 10:20:31 -0400 (EDT)
Chunyu Hu wrote:
> I tried the patch, if just for resolving the oops issue, it's indeed enough.
> But if we care about just this filter, and compare this with the
> trace_graph_entry
> filter handling, I found that, the depth 0 item will be submitted to
- Original Message -
> From: "Steven Rostedt" <rost...@goodmis.org>
> To: "Chunyu Hu" <ch...@redhat.com>
> Cc: linux-kernel@vger.kernel.org
> Sent: Wednesday, June 22, 2016 9:08:14 PM
> Subject: Re: [PATCH] tracing: Fix oops caused by grap
- Original Message -
> From: "Steven Rostedt"
> To: "Chunyu Hu"
> Cc: linux-kernel@vger.kernel.org
> Sent: Wednesday, June 22, 2016 9:08:14 PM
> Subject: Re: [PATCH] tracing: Fix oops caused by graph notrace filter
>
> On Tue, 21 J
On Tue, 21 Jun 2016 18:57:46 +0800
Chunyu Hu wrote:
> wakeup tracer can use function_graph trace when display_graph trace
> option is setup by user via tracefs, and bypass the set_graph_function
> and set_graph_notrace. But the bypass of set_graph_notrace is not clean.
>
On Tue, 21 Jun 2016 18:57:46 +0800
Chunyu Hu wrote:
> wakeup tracer can use function_graph trace when display_graph trace
> option is setup by user via tracefs, and bypass the set_graph_function
> and set_graph_notrace. But the bypass of set_graph_notrace is not clean.
> Although
- Original Message -
> From: "kbuild test robot" <l...@intel.com>
> To: "Chunyu Hu" <ch...@redhat.com>
> Cc: kbuild-...@01.org, rost...@goodmis.org, linux-kernel@vger.kernel.org
> Sent: Tuesday, June 21, 2016 8:39:22 PM
> Subject: Re: [P
- Original Message -
> From: "kbuild test robot"
> To: "Chunyu Hu"
> Cc: kbuild-...@01.org, rost...@goodmis.org, linux-kernel@vger.kernel.org
> Sent: Tuesday, June 21, 2016 8:39:22 PM
> Subject: Re: [PATCH] tracing: Fix oops caused by graph notrace fi
Hi,
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.7-rc4 next-20160621]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi,
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.7-rc4 next-20160621]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi,
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.7-rc4 next-20160621]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi,
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.7-rc4 next-20160621]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
wakeup tracer can use function_graph trace when display_graph trace
option is setup by user via tracefs, and bypass the set_graph_function
and set_graph_notrace. But the bypass of set_graph_notrace is not clean.
Although wakeup_graph_entry does most of the bypass, and both the enry
and exit event
wakeup tracer can use function_graph trace when display_graph trace
option is setup by user via tracefs, and bypass the set_graph_function
and set_graph_notrace. But the bypass of set_graph_notrace is not clean.
Although wakeup_graph_entry does most of the bypass, and both the enry
and exit event
18 matches
Mail list logo