From: "tip-bot for H. Peter Anvin" <hpa@linux.intel.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
stable@vger.kernel.org, robert.richter@amd.com,
jun.zhang@intel.com, tglx@linutronix.de, hpa@linux.intel.com,
wei.yang@windriver.com
Subject: [tip:x86/urgent] x86-32: Export kernel_stack_pointer() for modules
Date: Tue, 20 Nov 2012 23:35:40 -0800 [thread overview]
Message-ID: <tip-cb57a2b4cff7edf2a4e32c0163200e9434807e0a@git.kernel.org> (raw)
In-Reply-To: <20120912135059.GZ8285@erda.amd.com>
Commit-ID: cb57a2b4cff7edf2a4e32c0163200e9434807e0a
Gitweb: http://git.kernel.org/tip/cb57a2b4cff7edf2a4e32c0163200e9434807e0a
Author: H. Peter Anvin <hpa@linux.intel.com>
AuthorDate: Tue, 20 Nov 2012 22:21:02 -0800
Committer: H. Peter Anvin <hpa@linux.intel.com>
CommitDate: Tue, 20 Nov 2012 22:23:23 -0800
x86-32: Export kernel_stack_pointer() for modules
Modules, in particular oprofile (and possibly other similar tools)
need kernel_stack_pointer(), so export it using EXPORT_SYMBOL_GPL().
Cc: Yang Wei <wei.yang@windriver.com>
Cc: Robert Richter <robert.richter@amd.com>
Cc: Jun Zhang <jun.zhang@intel.com>
Cc: <stable@vger.kernel.org>
Link: http://lkml.kernel.org/r/20120912135059.GZ8285@erda.amd.com
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
---
arch/x86/kernel/ptrace.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/x86/kernel/ptrace.c b/arch/x86/kernel/ptrace.c
index 2484e33..5e0596b 100644
--- a/arch/x86/kernel/ptrace.c
+++ b/arch/x86/kernel/ptrace.c
@@ -22,6 +22,7 @@
#include <linux/perf_event.h>
#include <linux/hw_breakpoint.h>
#include <linux/rcupdate.h>
+#include <linux/module.h>
#include <asm/uaccess.h>
#include <asm/pgtable.h>
@@ -193,6 +194,7 @@ unsigned long kernel_stack_pointer(struct pt_regs *regs)
return (unsigned long)regs;
}
+EXPORT_SYMBOL_GPL(kernel_stack_pointer);
static unsigned long *pt_regs_access(struct pt_regs *regs, unsigned long regno)
{
prev parent reply other threads:[~2012-11-21 7:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 1:32 [PATCH 1/1] x86/oprofile: Fix the calltrace upon profiling some specified events with oprofile Wei.Yang
2012-08-28 9:17 ` Robert Richter
2012-09-03 5:28 ` wyang1
2012-09-04 10:24 ` Robert Richter
2012-09-06 1:30 ` wyang1
2012-09-06 10:04 ` [PATCH] x86, 32-bit: Fix invalid stack address while in softirq Robert Richter
2012-09-06 13:14 ` Steven Rostedt
2012-09-06 15:02 ` Robert Richter
2012-09-06 15:14 ` Steven Rostedt
2012-09-06 15:34 ` Robert Richter
2012-09-06 15:36 ` Robert Richter
2012-09-06 15:54 ` Steven Rostedt
2012-09-07 5:21 ` wyang1
2012-09-12 13:50 ` [PATCH -v2] " Robert Richter
2012-09-12 14:04 ` Steven Rostedt
2012-10-01 12:21 ` Robert Richter
2012-11-01 21:34 ` [tip:x86/urgent] x86-32: " tip-bot for Robert Richter
2012-11-13 15:17 ` Ingo Molnar
2012-11-13 15:56 ` Robert Richter
2012-11-15 21:53 ` tip-bot for Robert Richter
2012-11-21 7:34 ` tip-bot for Robert Richter
2012-11-21 7:35 ` tip-bot for H. Peter Anvin [this message]
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=tip-cb57a2b4cff7edf2a4e32c0163200e9434807e0a@git.kernel.org \
--to=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jun.zhang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=robert.richter@amd.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=wei.yang@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).