From: Alexander Beregalov <a.beregalov@gmail•com>
To: davem@davemloft•net, sparclinux@vger•kernel.org,
linux-next@vger•kernel.org, kenchen@google•com, mingo@elte•hu,
adobriyan@gmail•com
Subject: [PATCH] sparc64: add function save_stack_trace_tsk()
Date: Wed, 12 Nov 2008 16:47:49 +0300 [thread overview]
Message-ID: <20081112134749.GD12456@orion> (raw)
Hi
Current -next does not build on sparc64:
LD .tmp_vmlinux1
fs/built-in.o: In function `proc_pid_stack':
/home/alexb/linux-2.6/fs/proc/base.c:360: undefined reference to
`save_stack_trace_tsk'
---
Add function save_stack_trace_tsk() on sparc64.
Signed-off-by: Alexander Beregalov <a.beregalov@gmail•com>
---
arch/sparc64/kernel/stacktrace.c | 10 ++++++++--
1 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/arch/sparc64/kernel/stacktrace.c b/arch/sparc64/kernel/stacktrace.c
index 4e21d4a..a22eb8e 100644
--- a/arch/sparc64/kernel/stacktrace.c
+++ b/arch/sparc64/kernel/stacktrace.c
@@ -7,9 +7,9 @@
#include "kstack.h"
-void save_stack_trace(struct stack_trace *trace)
+void save_stack_trace_tsk(struct task_struct *tsk, struct stack_trace *trace)
{
- struct thread_info *tp = task_thread_info(current);
+ struct thread_info *tp = task_thread_info(tsk);
unsigned long ksp, fp;
stack_trace_flush();
@@ -47,4 +47,10 @@ void save_stack_trace(struct stack_trace *trace)
trace->entries[trace->nr_entries++] = pc;
} while (trace->nr_entries < trace->max_entries);
}
+EXPORT_SYMBOL_GPL(save_stack_trace_tsk);
+
+inline void save_stack_trace(struct stack_trace *trace)
+{
+ save_stack_trace_tsk(current, trace);
+}
EXPORT_SYMBOL_GPL(save_stack_trace);
next reply other threads:[~2008-11-12 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 13:47 Alexander Beregalov [this message]
2008-11-12 14:13 ` [PATCH] sparc64: add function save_stack_trace_tsk() Alexander Beregalov
2008-11-12 21:49 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081112134749.GD12456@orion \
--to=a.beregalov@gmail$(echo .)com \
--cc=adobriyan@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=kenchen@google$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=sparclinux@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox