mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: cmetcalf@tilera.com
Cc: linux-kernel@vger.kernel.org, Simon Marchi <simon.marchi@polymtl.ca>
Subject: [PATCH 2/3] arch/tile: Implement user_stack_pointer
Date: Sat, 22 Dec 2012 00:21:11 -0500	[thread overview]
Message-ID: <1356153672-17545-2-git-send-email-simon.marchi@polymtl.ca> (raw)
In-Reply-To: <1356153672-17545-1-git-send-email-simon.marchi@polymtl.ca>

It is needed when we turn on HAVE_ARCH_TRACEHOOK.

Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
---
 arch/tile/include/asm/ptrace.h |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/arch/tile/include/asm/ptrace.h b/arch/tile/include/asm/ptrace.h
index 5ce052e..4be42fb 100644
--- a/arch/tile/include/asm/ptrace.h
+++ b/arch/tile/include/asm/ptrace.h
@@ -80,6 +80,11 @@ struct task_struct;
 extern void send_sigtrap(struct task_struct *tsk, struct pt_regs *regs,
 			 int error_code);
 
+static inline unsigned long user_stack_pointer(struct pt_regs *regs)
+{
+	return regs->sp;
+}
+
 #ifdef __tilegx__
 /* We need this since sigval_t has a user pointer in it, for GETSIGINFO etc. */
 #define __ARCH_WANT_COMPAT_SYS_PTRACE
-- 
1.7.1


  reply	other threads:[~2012-12-22  5:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-22  5:21 [PATCH 1/3] arch/tile: Call tracehook_report_syscall_{entry,exit} in syscall trace Simon Marchi
2012-12-22  5:21 ` Simon Marchi [this message]
2012-12-22  6:03   ` [PATCH 2/3] arch/tile: Implement user_stack_pointer Al Viro
2012-12-22  5:21 ` [PATCH 3/3] arch/tile: Enable HAVE_ARCH_TRACEHOOK Simon Marchi
2012-12-26 18:42 ` [PATCH 1/3] arch/tile: Call tracehook_report_syscall_{entry,exit} in syscall trace Chris Metcalf

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=1356153672-17545-2-git-send-email-simon.marchi@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=cmetcalf@tilera.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®