systemtap_with_examples
  • Introduction
  • Installation
    • Build systap from source
    • Build package from source
  • Systemtap Language
    • Syntax
    • Variables
    • Control Flow
    • Function & Macro
    • TypeCase
    • Guru Mode
    • Probe Point
    • Predefined Functions
  • Examples
    • Call Graph
    • Dump Stack Trace
    • Duration
    • CPU Performance
    • Network DEV Analysis
    • KVM MMU
  • Reference
Powered by GitBook
On this page

Was this helpful?

  1. Systemtap Language

Probe Point

PreviousGuru ModeNextPredefined Functions

Last updated 6 years ago

Was this helpful?

As we may see, the syntax of systemtap is

probe PROBEPOINT [, PROBEPOINT] { [STMT ...] }

Probe point is the event to trigger the probe.

Here I will list some categories I have used. For more information, please refer to and .

begin, end
timer.s(1)
vfs.read
kernel.function("alloc_pages*")
kernel.statement("*@mm/page_alloc.c:3663")
module("kvm").function("kvm_init")
process("/usr/bin/vi").begin

To get more information about a probe point, you could use -L option to query.

For example, you want to know all the probe point in vfs subsystem, you could run

sudo stap -L 'vfs.*'

While I am wondering besides vfs, what are the other subsystems I could probe?

stapprobe
Built in probe point