3.1. Architecture
A SystemTap session begins when you run a SystemTap script. This session occurs in the following fashion:
Procedure 3.1. SystemTap Session
-
First, SystemTap checks the script against the existing tapset library (normally in /usr/share/systemtap/tapset/ for any tapsets used. SystemTap will then substitute any located
tapsets with their corresponding definitions in the tapset library.
-
SystemTap then translates the script to C, running the system C
compiler to create a kernel module from it. The tools that perform this
step are contained in the systemtap package (refer to
Section 2.1.1, “Installing SystemTap” for more information).
-
SystemTap loads the module, then enables all the probes (events and handlers) in the script. The staprun in the systemtap-runtime package (refer to
Section 2.1.1, “Installing SystemTap” for more information) provides this functionality.
-
As the events occur, their corresponding handlers are executed.
-
Once the SystemTap session is terminated, the probes are disabled, and the kernel module is unloaded.
阅读(931) | 评论(0) | 转发(0) |
