From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/25218] stapbpf loses perf_events when writing to interactive terminal
Date: Mon, 25 Nov 2019 18:22:00 -0000 [thread overview]
Message-ID: <bug-25218-6586-3wJtgKrTis@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25218-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25218
--- Comment #2 from Serhei Makarov <me at serhei dot io> ---
One thing that I should definitely fix, aside from tackling the speed disparity
in console/file output: when perf_events are lost, unpaired PRINTF_{START,END}
messages should not cause a fatal error for stapbpf.
That is, a sequence such as
PRINTF_START PRINTF_END <lost events> PRINTF_END
should cause the PRINTF_END to be dropped along with the lost events.
Currently it causes stapbpf to terminate with an error message.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2019-11-25 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 23:13 [Bug bpf/25218] New: stapbpf losing perf_events sapatel at redhat dot com
2019-11-22 23:16 ` [Bug bpf/25218] " sapatel at redhat dot com
2019-11-22 23:46 ` [Bug bpf/25218] stapbpf loses perf_events when writing to interactive terminal me at serhei dot io
2019-11-25 18:22 ` me at serhei dot io [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=bug-25218-6586-3wJtgKrTis@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).