Add chng_cpu.stp and migrate.stp examples.

1 files changed, 23 insertions, 0 deletions

diff --git a/testsuite/systemtap.examples/index.txt b/testsuite/systemtap.examples/index.txt
index 49a7e89b..98d96302 100644
--- a/testsuite/systemtap.examples/index.txt
+++ b/testsuite/systemtap.examples/index.txt
@@ -261,6 +261,18 @@ keywords: network statistics
   and grouped by individual sockets.
 
 
+process/chng_cpu.stp - Monitor Changes in Processor Executing a Task
+keywords: scheduler
+
+  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.
+
+
 process/errsnoop.stp - tabulate system call errors
 keywords: process syscall
 
@@ -288,6 +300,17 @@ keywords: syscall locking futex
   highest.
 
 
+process/migrate.stp - Track the Migration of Specific Executables
+keywords: scheduler
+
+  The migrate.stp script takes an argument which is the executable name
+  of the task it should monitor. Each time a task with that executable
+  name migrates between processors an entry is printed with the process
+  id (pid), the executable name, the processor off loading the task,
+  and the process taking the task. Note that the task may or may not be
+  executing at the time of the migration.
+
+
 process/pf2.stp - Profile kernel functions
 keywords: profiling