public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mjw@redhat.com>
To: Wade Farnsworth <wade_farnsworth@mentor.com>
Cc: systemtap@sourceware.org
Subject: Re: [PATCH v2] ARM uprobes support
Date: Wed, 23 Nov 2011 14:17:00 -0000	[thread overview]
Message-ID: <1322057831.20984.10.camel@springer.wildebeest.org> (raw)
In-Reply-To: <4EB43E69.40004@mentor.com>

Hi Wade,

On Fri, 2011-11-04 at 12:35 -0700, Wade Farnsworth wrote:
> Basic uprobes support for ARM.
> 
> Signed-off-by: Wade Farnsworth <wade_farnsworth@mentor.com>

Sorry for the long delay in applying this. I had some troubles getting a
working arm setup. I was using a pre-3.0 kernel, but arm kprobes before
3.0 seems somewhat unstable. I now use a 2.6.40.4-6.fc15.armv7hl.tegra
kernel on a trimslice (fedora uses a somewhat strange numbering here,
2.6.40.4 == 3.0.4) which seems stable and is able to complete a full
make installcheck testrun. But of course it doesn't have the needed
tracehook and user_regset patches in the kernel, so I still wasn't able
to test your uprobes work. But it seemed a shame to not have the patch
in to make it easier for others to test. My arm foo is very limited, but
the new code doesn't affect anything else.

commit be898cc4485951b10e692932a49144b5a00deef1
Author: Wade Farnsworth <wade_farnsworth@mentor.com>
Date:   Fri Nov 4 12:35:05 2011 -0700

    ARM uprobes support
    
    Basic uprobes support for ARM.
    
    Signed-off-by: Wade Farnsworth <wade_farnsworth@mentor.com>

Hopefully I'll get the user_regset and tracehook patches in my kernel
soon to properly test it. Do you know if anybody is pushing these
patches upstream into the mainline kernel?

Have you ran make installcheck on your setup? And could you share the
results? Mine can be found at:
http://web.elastic.org/~dejazilla/viewsummary.php?summary=%3D%27%
3C20111123084132.D731F4C6CB%40springer.wildebeest.org%3E%27

Thanks,

Mark

  reply	other threads:[~2011-11-23 14:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03 18:07 [PATCH 0/2] Userspace tap support for ARM Wade Farnsworth
2011-11-03 18:08 ` [PATCH 1/2] " Wade Farnsworth
2011-11-03 18:13   ` [PATCH 1/2] Add syscall information " Wade Farnsworth
2011-11-04 12:12     ` Mark Wielaard
2011-11-03 18:09 ` [PATCH 2/2] ARM uprobes support Wade Farnsworth
2011-11-04 19:35   ` [PATCH v2] " Wade Farnsworth
2011-11-23 14:17     ` Mark Wielaard [this message]
2011-11-03 20:36 ` [PATCH 0/2] Userspace tap support for ARM Wade Farnsworth
2011-11-04  9:05   ` Mark Wielaard
     [not found]     ` <4EB3F998.7030305@mentor.com>
2011-11-04 19:41       ` 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=1322057831.20984.10.camel@springer.wildebeest.org \
    --to=mjw@redhat.com \
    --cc=systemtap@sourceware.org \
    --cc=wade_farnsworth@mentor.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 read-only IMAP folder(s) and NNTP newsgroup(s).