On Thu, 22 Nov 2018 22:11:33 -0800
Joel Fernandes wrote:
> On Wed, Nov 21, 2018 at 08:27:14PM -0500, Steven Rostedt wrote:
> > From: "Steven Rostedt (VMware)"
> >
> > To make the function graph infrastructure more managable, the code needs to
> > be in its own file (fgraph.c). Move the code tha
On Fri, Nov 23, 2018 at 01:11:38PM -0500, Steven Rostedt wrote:
> On Fri, 23 Nov 2018 12:58:34 -0500
> Steven Rostedt wrote:
>
> > I think the better answer is to move it into trace_functions_graph.c.
>
> I take that back. I think the better answer is to not call that
> function if the profiler
On Fri, 23 Nov 2018 12:58:34 -0500
Steven Rostedt wrote:
> I think the better answer is to move it into trace_functions_graph.c.
I take that back. I think the better answer is to not call that
function if the profiler is not set, nor have that option even
available. Because it has no meaning wit
On Thu, 22 Nov 2018 22:11:33 -0800
Joel Fernandes wrote:
> On Wed, Nov 21, 2018 at 08:27:14PM -0500, Steven Rostedt wrote:
> > From: "Steven Rostedt (VMware)"
> >
> > To make the function graph infrastructure more managable, the code needs to
> > be in its own file (fgraph.c). Move the code tha
On Wed, Nov 21, 2018 at 08:27:14PM -0500, Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> To make the function graph infrastructure more managable, the code needs to
> be in its own file (fgraph.c). Move the code that is specific for managing
> the function graph infrastructure out of
From: "Steven Rostedt (VMware)"
To make the function graph infrastructure more managable, the code needs to
be in its own file (fgraph.c). Move the code that is specific for managing
the function graph infrastructure out of ftrace.c and into fgraph.c
Signed-off-by: Steven Rostedt (VMware)
---
6 matches
Mail list logo
