linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM tracehook support
Date: Mon, 20 Feb 2012 15:47:48 +0000	[thread overview]
Message-ID: <20120220154748.GG25462@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <4F4268D5.7070103@mentor.com>

On Mon, Feb 20, 2012 at 03:37:57PM +0000, Wade Farnsworth wrote:
> Hi all,

Hello Wade,

> A few months back, Steven Walter posted some patches that implemement 
> syscall tracing support for ARM:
> 
> http://lists.arm.linux.org.uk/lurker/message/20111129.162812.bd17d9b5.en.html#linux-arm-kernel
> 
> I've been working on SystemTap support for ARM, and the tracehook patch 
> in particular is interesting in that respect.  With that patch applied, 
> it would allow utrace to be supported on ARM, which is necessary for 
> userspace stap probes to function properly.
> 
>  From what testing I've done, the patches don't appear to be harmful. 
> So, I'm wondering what's preventing this from being pushed into 
> mainline?  Are there still outstanding issues that need to be addressed? 

Yup, I posted some questions here:

http://lists.infradead.org/pipermail/linux-arm-kernel/2011-December/074802.html

but I haven't heard anything from Steven since then, so it's all stalled at
the moment. They'll also obviously need rebasing onto latest mainline,
although that shouldn't be too hard since they're still fairly recent.

Will

  reply	other threads:[~2012-02-20 15:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20 15:37 ARM tracehook support Wade Farnsworth
2012-02-20 15:47 ` Will Deacon [this message]
2012-02-20 18:08   ` Wade Farnsworth
2012-02-21 17:06     ` Wade Farnsworth
2012-02-21 17:24       ` Will Deacon
2012-02-21 17:30         ` Russell King - ARM Linux
2012-02-21 17:27     ` Russell King - ARM Linux
2012-02-21 18:08       ` Wade Farnsworth

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=20120220154748.GG25462@mudshark.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).