From: "Olausson, Bjoern" <contactme@olausson.de>
To: "Frank Ch. Eigler" <fche@redhat.com>, systemtap@sourceware.org
Subject: Re: Using systemtap on MPI applications
Date: Thu, 17 Mar 2016 12:51:00 -0000 [thread overview]
Message-ID: <CAE7O3Tf0fxhQOusWsoD=_oRCOZ+vUj_49aAL=fa1x6xzWdBG5A@mail.gmail.com> (raw)
In-Reply-To: <20160317124917.GC29879@redhat.com>
On Thu, Mar 17, 2016 at 1:49 PM, Frank Ch. Eigler <fche@redhat.com> wrote:
> Hi -
>
>> Excuse that stupid question, but I thought using "-c CMD" will always
>> instantly execute the CMD, so that would not play will with MPI
>> executed applications :)
>
> Not exactly - "stap -c CMD" should run CMD at each --remote site.
> The extent to which an mpi CMD would run correctly though (and find
> its MPI peers etc.) is unknown though.
>
>> But is there a way to pass a string to stap on which I can apply e.g.
>> your above filter instead of hardcoding the exec name I want to filter
>> on?
>
> Certainly; command line options or global variables are two of the ways.
> The latter performs better because it permits caching.
>
> stap -e 'probe something { if (execname() == @1) { ...} }' bar
> stap -e 'global foo; probe something { if (execname() == foo) { ...} }' -Gfoo=bar
>
> - FChE
Thanks a lot, that makes things way easier!
Cheers,
Bjoern
next prev parent reply other threads:[~2016-03-17 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 14:24 Olausson, Bjoern
2016-03-15 19:09 ` Frank Ch. Eigler
2016-03-16 8:13 ` Olausson, Bjoern
2016-03-16 14:07 ` Frank Ch. Eigler
2016-03-17 12:10 ` Olausson, Bjoern
[not found] ` <CAE7O3Tcg7317VY5eH_ipqP7wqUR9CnwmCsdU4z+=wVbv3y14SQ@mail.gmail.com>
[not found] ` <20160317124917.GC29879@redhat.com>
2016-03-17 12:51 ` Olausson, Bjoern [this message]
2016-05-02 15:40 ` Olausson, Bjoern
2016-05-02 15:25 ` Frank Ch. Eigler
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='CAE7O3Tf0fxhQOusWsoD=_oRCOZ+vUj_49aAL=fa1x6xzWdBG5A@mail.gmail.com' \
--to=contactme@olausson.de \
--cc=fche@redhat.com \
--cc=systemtap@sourceware.org \
/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).