This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Using systemtap on MPI applications
- From: "Frank Ch. Eigler" <fche at redhat dot com>
- To: "Olausson, Bjoern" <contactme at olausson dot de>
- Cc: systemtap at sourceware dot org
- Date: Wed, 16 Mar 2016 10:07:24 -0400
- Subject: Re: Using systemtap on MPI applications
- Authentication-results: sourceware.org; auth=none
- References: <CAE7O3Td1P1jFFbbBFu5k+uu8w8Zw9+fSgRYJqc7d4H57dAV09A at mail dot gmail dot com> <y0mh9g7a77l dot fsf at fche dot csb> <CAE7O3TfvL=7YmYeEyo=MrKM7T8ph_PMqgxYGko-BtzyHGLaf4Q at mail dot gmail dot com>
Hi -
> > "Olausson, Bjoern" wrote:
> Indeed it would be great if stap would be MPI aware in some way.
"patches welcome" :-) we'd be glad to advise, but aren't planning
to undertake the work ourselves very soon.
> Still there is the issue on how to filter what stap is tracing. How
> would I tell stap to only focus on one particular executable or PID
> when using the --remote switch so target() can be used.
> Any ideas on that?
I believe the "stap -c CMD" and "stap -x PID" options both travel
through "stap --remote ..." ssh, though of course the former makes a
lot more sense. The "-c CMD" may be good enough for MPI purposes.
And there's always filtering from first principles:
if (execname() =~ ".*foo.*" && uid() == 44) { }
- FChE