From: Mark Wielaard <mjw@redhat.com>
To: William Cohen <wcohen@redhat.com>
Cc: David Smith <dsmith@redhat.com>, systemtap@sourceware.org
Subject: Re: Recent review of SystemTap test results on ARM running Fedora 15 hard float.
Date: Mon, 27 Feb 2012 21:54:00 -0000 [thread overview]
Message-ID: <20120227215420.GB6644@toonder.wildebeest.org> (raw)
In-Reply-To: <1330359008.2736.60.camel@springer.wildebeest.org>
On Mon, Feb 27, 2012 at 05:10:08PM +0100, Mark Wielaard wrote:
> On Mon, 2012-02-27 at 10:33 -0500, William Cohen wrote:
> > Does this this test need the uprobes support for this test to work?
>
> Maybe... I am a little fuzzy on the details of when/how vma tracking is
> triggered. Technically vma tracking doesn't need uprobes. But it might
> be that vma tracking is only enabled/started if uprobes are active. You
> might have to look with -DDEBUG_TASK_FINDER_VMA to see what is
> happening.
I poked a bit myself on an arm setup. The vma tracker doesn't need
uprobes, but it does need the task finder, and runtime.h says:
#if (defined(CONFIG_UTRACE) || defined(STAPCONF_UTRACE_VIA_TRACEPOINTS) \
|| defined(STAPCONF_UTRACE_VIA_FTRACE))
#define HAVE_TASK_FINDER
#endif
So you do need some form of UTRACE.
Unfortunately my setup doesn't have that.
Does your kernel?
Cheers,
Mark
next prev parent reply other threads:[~2012-02-27 21:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 19:06 William Cohen
2012-02-23 20:55 ` David Smith
2012-02-23 22:06 ` William Cohen
2012-02-23 22:56 ` David Smith
2012-02-24 16:04 ` David Smith
2012-02-24 18:27 ` William Cohen
2012-02-24 19:28 ` David Smith
2012-02-24 21:49 ` William Cohen
2012-02-25 19:40 ` Mark Wielaard
2012-02-27 15:33 ` William Cohen
2012-02-27 16:10 ` Mark Wielaard
2012-02-27 21:54 ` Mark Wielaard [this message]
2012-02-27 22:20 ` William Cohen
2012-02-23 22:12 ` David Smith
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=20120227215420.GB6644@toonder.wildebeest.org \
--to=mjw@redhat.com \
--cc=dsmith@redhat.com \
--cc=systemtap@sourceware.org \
--cc=wcohen@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).