Bug 597329 - Backport the uprobes singlestep bypass
Backport the uprobes singlestep bypass
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: systemtap (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Frank Ch. Eigler
Petr Muller
Depends On:
  Show dependency treegraph
Reported: 2010-05-28 12:34 EDT by Josh Stone
Modified: 2016-09-19 22:06 EDT (History)
3 users (show)

See Also:
Fixed In Version: systemtap-1.2-5.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-10 16:44:43 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Josh Stone 2010-05-28 12:34:33 EDT
A recent change in systemtap's uprobes kernel module lets it skip singlestepping after a breakpoint on easily emulated instructions, especially NOPs.


This is significant for SDT, our userspace static probes, because those probes always insert a NOP for systemtap to put a breakpoint on.  Using our benchmark scripts/probe_perf/bench.sh, which measures the overhead of nearly 4 million probe hits, I get these elapsed times:

   not instrumented:  0.86s
   uprobes w/ sstep: 16.46s
  uprobes w/o sstep:  7.81s

I believe this is a very worthwhile and easy change to backport into RHEL's systemtap package.
Comment 1 Josh Stone 2010-06-09 15:02:47 EDT
This commit is needed to fix powerpc:


We are also waiting on IBM folks to see if we need additions in powerpc's arch_validate_probed_insn().
Comment 2 Josh Stone 2010-06-14 18:53:09 EDT
uprobes_ppc: Don't emulate privileged MSR opcodes

(FLW) I believe it's good to go...
Comment 5 releng-rhel@redhat.com 2010-11-10 16:44:43 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.