From: fche@redhat.com (Frank Ch. Eigler)
To: ananth@in.ibm.com
Cc: Diptopal Basu <diptopal.basu@gmail.com>,
systemtap@sourceware.org, utrace-devel@redhat.com
Subject: Re: Need more information on uProbes .
Date: Tue, 31 Mar 2009 15:06:00 -0000 [thread overview]
Message-ID: <y0mzlf13ht5.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <20090331130632.GA6358@in.ibm.com> (Ananth N. Mavinakayanahalli's message of "Tue, 31 Mar 2009 18:36:32 +0530")
ananth wrote:
> Uprobes is implemented only for architectures that have utrace support
> (x86-32, x86_64, powerpc, s390, but not IA64). [...]
(HAVE_ARCH_TRACEHOOK is on for ia64, sparc, sh also, so utrace per se
should work there.)
> [...] For ARM though, the utrace layer needs to be implemented and
> uprobes ported over. [...]
Roland et al., has there been any recent report on
regset/tracehook-on-arm porting?
- FChE
next prev parent reply other threads:[~2009-03-31 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 13:14 Diptopal Basu
2009-03-31 14:11 ` Ananth N Mavinakayanahalli
2009-03-31 15:06 ` Frank Ch. Eigler [this message]
2009-03-31 17:57 ` Jim Keniston
2009-03-31 23:02 ` Roland McGrath
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=y0mzlf13ht5.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=ananth@in.ibm.com \
--cc=diptopal.basu@gmail.com \
--cc=systemtap@sourceware.org \
--cc=utrace-devel@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).