[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20181221.102414.1992688460948808079.davem@davemloft.net>
Date: Fri, 21 Dec 2018 10:24:14 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: rostedt@...dmis.org
Cc: linux-kernel@...r.kernel.org, mingo@...nel.org,
akpm@...ux-foundation.org, namhyung@...nel.org,
mhiramat@...nel.org, sparclinux@...r.kernel.org
Subject: Re: [for-next][PATCH 06/24] sparc64: Use
ftrace_graph_get_ret_stack() instead of curr_ret_stack
From: Steven Rostedt <rostedt@...dmis.org>
Date: Fri, 21 Dec 2018 12:56:24 -0500
> From: "Steven Rostedt (VMware)" <rostedt@...dmis.org>
>
> The structure of the ret_stack array on the task struct is going to
> change, and accessing it directly via the curr_ret_stack index will no
> longer give the ret_stack entry that holds the return address. To access
> that, architectures must now use ftrace_graph_get_ret_stack() to get the
> associated ret_stack that matches the saved return address.
>
> Cc: sparclinux@...r.kernel.org
> Cc: "David S. Miller" <davem@...emloft.net>
> Signed-off-by: Steven Rostedt (VMware) <rostedt@...dmis.org>
Acked-by: David S. Miller <davem@...emloft.net>
Powered by blists - more mailing lists