From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 111829 invoked by alias); 22 Nov 2019 23:46:38 -0000 Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org Received: (qmail 111780 invoked by uid 48); 22 Nov 2019 23:46:34 -0000 From: "me at serhei dot io" To: systemtap@sourceware.org Subject: [Bug bpf/25218] stapbpf loses perf_events when writing to interactive terminal Date: Fri, 22 Nov 2019 23:46:00 -0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: bpf X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: me at serhei dot io X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2019-q4/txt/msg00047.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3D25218 Serhei Makarov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |me at serhei dot io Summary|stapbpf losing perf_events |stapbpf loses perf_events | |when writing to interactive | |terminal --- Comment #1 from Serhei Makarov --- My suspicion is that the perf_events buffer used to receive transport messa= ges fills up while the stapbpf process is delayed writing output. This results = in transport messages being overwritten and the 'lost perf_events' warning bei= ng generated. When stapbpf output is redirected to a file, there is no I/O delay, and perf_events are consumed before the buffer overflows. If my suspicion is true, this could be solved by receiving transport messag= es in a separate thread. --=20 You are receiving this mail because: You are the assignee for the bug.