public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "agentzh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/27877] New: Missing -t timing stats support in the bpf backend
Date: Mon, 17 May 2021 18:50:29 +0000	[thread overview]
Message-ID: <bug-27877-6586@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=27877

            Bug ID: 27877
           Summary: Missing -t timing stats support in the bpf backend
           Product: systemtap
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: bpf
          Assignee: systemtap at sourceware dot org
          Reporter: agentzh at gmail dot com
  Target Milestone: ---

Currently the bpf backend lacks probe timing stats enabled by the `-t` CLI
option, as evidenced by the following example:

```
$ /opt/stap/bin/stap -t --bpf -e 'probe oneshot { println("Hello world") }'
Hello world
```

For comparison, the default kernel backend runs fine:

```
$ /opt/stap/bin/stap -t -e 'probe oneshot { println("Hello world") }'
Hello world
----- probe hit report:
begin, (<input>:1:7), hits: 1, cycles: 2880min/2880avg/2880max, variance: 0,
from: oneshot from: oneshot, index: 0
----- refresh report:
```

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2021-05-17 18:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 18:50 agentzh at gmail dot com [this message]
2023-01-13 11:38 ` [Bug bpf/27877] " dichen at redhat dot com
2023-01-14 19:13 ` agentzh at gmail dot com
2023-02-06 14:27 ` dichen at redhat dot com

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=bug-27877-6586@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --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).