From deb635455c042a10cc74a45c9ef02458d890946f Mon Sep 17 00:00:00 2001 From: William Cohen Date: Fri, 17 Jul 2009 15:18:51 -0400 Subject: Add chng_cpu.stp and migrate.stp examples. --- testsuite/systemtap.examples/process/chng_cpu.meta | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 testsuite/systemtap.examples/process/chng_cpu.meta (limited to 'testsuite/systemtap.examples/process/chng_cpu.meta') diff --git a/testsuite/systemtap.examples/process/chng_cpu.meta b/testsuite/systemtap.examples/process/chng_cpu.meta new file mode 100644 index 00000000..944f417a --- /dev/null +++ b/testsuite/systemtap.examples/process/chng_cpu.meta @@ -0,0 +1,14 @@ +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: pid +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 -- cgit