aboutsummaryrefslogtreecommitdiff
path: root/kernel
diff options
context:
space:
mode:
authorTiejun Chen <tiejun.chen@windriver.com>2013-02-27 11:09:27 +0800
committerJason Wessel <jason.wessel@windriver.com>2013-03-02 08:52:17 -0600
commite78acf67ba7e32071e6eca14d8c39c7b1f130c31 (patch)
tree457450b97550e956f954a843a52f4a2ebbea1160 /kernel
parentf7c82d5a3c537a4b4d9d0395db4606bf4d3c7a5f (diff)
downloadvexpress-lsk-e78acf67ba7e32071e6eca14d8c39c7b1f130c31.tar.gz
kgdb/kgdbts: support ppc64
We can't look up the address of the entry point of the function simply via that function symbol for all architectures. For PPC64 ABI, actually there is a function descriptors structure. A function descriptor is a three doubleword data structure that contains the following values: * The first doubleword contains the address of the entry point of the function. * The second doubleword contains the TOC base address for the function. * The third doubleword contains the environment pointer for languages such as Pascal and PL/1. So we should call a wapperred dereference_function_descriptor() to get the address of the entry point of the function. Note this is also safe for other architecture after refer to "include/asm-generic/sections.h" since: dereference_function_descriptor(p) always is (p) if without arched definition. Signed-off-by: Tiejun Chen <tiejun.chen@windriver.com> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions