public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/24416] Tests stuck in uprobes_onthefly.exp
Date: Fri, 05 Apr 2019 16:00:00 -0000	[thread overview]
Message-ID: <bug-24416-6586-U3H5Qb2Rei@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24416-6586@http.sourceware.org/bugzilla/>

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

--- Comment #3 from William Cohen <wcohen at redhat dot com> ---
There looks to be some very hot tracepoints that are only appearing on the
fedora x86 5.0.x kernels that do not appear on rhel7 x86 or aarch64.  Follow
was run for only a short time:

$ sudo stap -ve 'global counts probe kernel.trace("*"){counts[pp()] <<< 1}'
Pass 1: parsed user script and 492 library scripts using
388652virt/161896res/9176shr/152916data kb, in 320usr/130sys/464real ms.
Pass 2: analyzed script: 758 probes, 1 function, 0 embeds, 1 global using
401280virt/175916res/10224shr/165544data kb, in 140usr/450sys/602real ms.
Pass 3: translated to C into
"/tmp/stapLJpHud/stap_7678d191c1a6333683c0dfbeb77bd4b6_207067_src.c" using
401792virt/176236res/10288shr/166056data kb, in 20usr/0sys/27real ms.
Pass 4: compiled C into "stap_7678d191c1a6333683c0dfbeb77bd4b6_207067.ko" in
44040usr/14440sys/60733real ms.
Pass 5: starting run.
^Ccounts["kernel.trace("lock:lock_release")"] @count=142050 @min=1 @max=1
@sum=142050 @avg=1
counts["kernel.trace("lock:lock_acquire")"] @count=142050 @min=1 @max=1
@sum=142050 @avg=1
counts["kernel.trace("lock:lock_acquired")"] @count=54136 @min=1 @max=1
@sum=54136 @avg=1
counts["kernel.trace("preemptirq:irq_enable")"] @count=53906 @min=1 @max=1
@sum=53906 @avg=1
counts["kernel.trace("preemptirq:irq_disable")"] @count=53906 @min=1 @max=1
@sum=53906 @avg=1
counts["kernel.trace("rcu:rcu_utilization")"] @count=6894 @min=1 @max=1
@sum=6894 @avg=1
counts["kernel.trace("msr:write_msr")"] @count=6275 @min=1 @max=1 @sum=6275
@avg=1
...

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

  parent reply	other threads:[~2019-04-05 16:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03 14:57 [Bug runtime/24416] New: " wcohen at redhat dot com
2019-04-03 16:11 ` [Bug runtime/24416] " wcohen at redhat dot com
2019-04-05 15:39 ` wcohen at redhat dot com
2019-04-05 16:00 ` wcohen at redhat dot com [this message]
2019-04-05 19:14 ` wcohen at redhat dot com
2019-04-05 21:25 ` wcohen at redhat dot com
2019-04-05 22:03 ` fche at redhat dot com
2019-04-08 14:10 ` wcohen at redhat dot com
2019-04-09 21:43 ` wcohen at redhat dot com
2019-04-10 21:11 ` wcohen 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-24416-6586-U3H5Qb2Rei@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).