Re: [RFC PATCH 1/6] trace/stack: Move code to save the stack trace into a separate function

2021-06-02 Thread Steven Rostedt
On Wed, 02 Jun 2021 16:05:18 +0530 "Naveen N. Rao" wrote: > It seems to be working fine otherwise. The one limitation though is down > to how ftrace works on powerpc -- the mcount call is before a function > sets up its own stackframe. Due to this, we won't ever be able to > account for the

Re: [RFC PATCH 1/6] trace/stack: Move code to save the stack trace into a separate function

2021-06-02 Thread Naveen N. Rao
Steven Rostedt wrote: On Fri, 21 May 2021 12:18:36 +0530 "Naveen N. Rao" wrote: In preparation to add support for stack tracer to powerpc, move code to save stack trace and to calculate the frame sizes into a separate weak function. Also provide access to some of the data structures used by

Re: [RFC PATCH 1/6] trace/stack: Move code to save the stack trace into a separate function

2021-06-01 Thread Steven Rostedt
On Fri, 21 May 2021 12:18:36 +0530 "Naveen N. Rao" wrote: > In preparation to add support for stack tracer to powerpc, move code to > save stack trace and to calculate the frame sizes into a separate weak > function. Also provide access to some of the data structures used by the > stack trace

[RFC PATCH 1/6] trace/stack: Move code to save the stack trace into a separate function

2021-05-21 Thread Naveen N. Rao
In preparation to add support for stack tracer to powerpc, move code to save stack trace and to calculate the frame sizes into a separate weak function. Also provide access to some of the data structures used by the stack trace code so that architectures can update those. Signed-off-by: Naveen N.