From: fche@redhat.com (Frank Ch. Eigler)
To: Brendan Gregg <brendan.d.gregg@gmail.com>
Cc: Richard Henderson <rth@redhat.com>,
systemtap@sourceware.org, iovisor-dev@lists.iovisor.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: BPF runtime for systemtap
Date: Wed, 15 Jun 2016 01:50:00 -0000 [thread overview]
Message-ID: <y0m1t3zi5js.fsf@fche.csb> (raw)
In-Reply-To: <CAE40pdftVg+vuDpYhwsuBj_Ptk9P+TrB3M4GDB0xtvEqxYEt2Q@mail.gmail.com> (Brendan Gregg's message of "Tue, 14 Jun 2016 16:53:58 -0700")
brendan.d.gregg wrote:
> [...]
> Great! Is there a hello world example in there somewhere? I found this:
> [...]
Yup. Here is a smoke test. (A great many other things are not yet
working.)
% sudo ./stap -v --runtime=bpf -e 'global foo
probe kprobe.function("vfs_read"), kprobe.function("do_select") { foo++ }
probe begin { printf("systemtap starting probe\n") }
probe end { printf("systemtap ending probe\n"); printf("foo = %d\n", foo) }'
Pass 1: parsed user script and 35 library scripts using 198460virt/15804res/6416shr/9208data kb, in 0usr/0sys/71real ms.
Pass 2: analyzed script: 4 probes, 0 functions, 0 embeds, 1 global using 198460virt/15804res/6416shr/9208data kb, in 0usr/0sys/0real ms.
Pass 4: compiled BPF into "stap_32349.bo" in 0usr/0sys/0real ms.
Pass 5: starting run.
systemtap starting probe
^Csystemtap ending probe
foo = 108812
Pass 5: run completed in 0usr/10sys/2525real ms.
prev parent reply other threads:[~2016-06-15 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 20:06 Richard Henderson
2016-06-14 23:54 ` Brendan Gregg
2016-06-15 1:50 ` Frank Ch. Eigler [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=y0m1t3zi5js.fsf@fche.csb \
--to=fche@redhat.com \
--cc=brendan.d.gregg@gmail.com \
--cc=iovisor-dev@lists.iovisor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@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).