[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151013114538.5d37ffc9@gandalf.local.home>
Date: Tue, 13 Oct 2015 11:45:38 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: AKASHI Takahiro <takahiro.akashi@...aro.org>
Cc: catalin.marinas@....com, will.deacon@....com,
jungseoklee85@...il.com, olof@...om.net, broonie@...nel.org,
david.griego@...aro.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 5/7] ftrace: allow arch-specific stack tracer
On Thu, 8 Oct 2015 19:01:42 +0900
AKASHI Takahiro <takahiro.akashi@...aro.org> wrote:
> include/linux/ftrace.h | 10 ++++++++++
> kernel/trace/trace_stack.c | 22 ++++++++++++++--------
> 2 files changed, 24 insertions(+), 8 deletions(-)
>
> diff --git a/include/linux/ftrace.h b/include/linux/ftrace.h
> index d77b195..e538400 100644
> --- a/include/linux/ftrace.h
> +++ b/include/linux/ftrace.h
> @@ -270,7 +270,17 @@ static inline void ftrace_kill(void) { }
> #define FTRACE_STACK_FRAME_OFFSET 0
> #endif
>
> +#define STACK_TRACE_ENTRIES 500
> +
> +struct stack_trace;
> +
> +extern unsigned stack_dump_index[];
> +extern struct stack_trace max_stack_trace;
> +extern unsigned long max_stack_size;
> +extern arch_spinlock_t max_stack_lock;
> +
> extern int stack_tracer_enabled;
> +void print_max_stack(void);
OK, if we are making these external, they need to have better name
space naming.
stack_dump_index => stack_trace_index
max_stack_trace => stack_trace_max
max_stack_size => stack_trace_max_size
print_max_stack() => stack_trace_print()
-- Steve
> int
> stack_trace_sysctl(struct ctl_table *table, int write,
> void __user *buffer, size_t *lenp,
> diff --git a/kernel/trace/trace_stack.c b/kernel/trace/trace_stack.c
> index 30521ea..ff1a191 100644
> --- a/kernel/trace/trace_stack.c
> +++ b/kernel/trace/trace_stack.c
> @@ -16,24 +16,22 @@
>
> #include "trace.h"
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists