public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: William Cohen <wcohen@redhat.com>
To: Quentin Barnes <qbarnes@urbana.css.mot.com>
Cc: systemtap@sources.redhat.com
Subject: Re: [RFC][PATCH] Kprobes for ARM
Date: Fri, 13 Apr 2007 20:02:00 -0000	[thread overview]
Message-ID: <461FE1E0.3000301@redhat.com> (raw)
In-Reply-To: <20070411061028.GA20808@urbana.css.mot.com>

Quentin Barnes wrote:
> This is a fully functional Kprobes implementation for ARM as a
> patch set against the 2.6.20.4 kernel.
> 
> This implementation includes kprobes, jprobes, and kretprobes.
> Abhishek Sagar contributed the initialization, undef handling, fault
> handling, jprobes, and kretprobes code.  The blame for the remaining
> core kprobes code falls to me.
> 
> This code has no known problems and has received some basic testing
> through systemtap testsuite.  It should, however, be considered
> raw prototype quality.  I'm sure it has a considerable quantity of
> undiscovered bugs.
> 
> This mail exceeds Linus' recommended size of 40KB for a patch
> mailing.  It is ~70KB in size.  However, I have noticed that others
> on this mailing list have exceeded the limit before.  If this size
> is an imposition, please let me know.  I'll be setting this project
> up on a remote site, but haven't yet.  This will probably be my
> only patch mailing of this size.
> 
> I'll provide more detailed information in some following mails.
> 
> Quentin

Hi Quentin,

Now that you have a kprobes implementation for ARM are you thinking about the 
modifications for the SystemTap translator to support cross compiling probes for 
ARM target?  There is a bugzilla #4186 looking at this issue for cross compiling 
subarchitectures e.g. i686 compiling probes (workstation) for i586 machine (olpc 
machine).

-Will

      parent reply	other threads:[~2007-04-13 20:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-11  6:11 Quentin Barnes
2007-04-13 19:17 ` Frank Ch. Eigler
2007-04-13 20:02 ` William Cohen [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=461FE1E0.3000301@redhat.com \
    --to=wcohen@redhat.com \
    --cc=qbarnes@urbana.css.mot.com \
    --cc=systemtap@sources.redhat.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).