This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
resolving probe point context_switch
- From: "Jason Yeh" <jason dot yeh at amd dot com>
- To: systemtap at sources dot redhat dot com
- Date: Thu, 12 Oct 2006 13:18:44 -0500
- Subject: resolving probe point context_switch
- References: <20061012152411.GA3979@redhat.com>
Hi,
I have been trying to get Systemtap to place probe in the scheduler and
hoping to experiment using Systemtap to emulate certain behavior of
Perfmon2 similar to what Frank mentioned in the email titled
"Model-Specific Register". Running the example sched_snoop.stp was
successful only on Athlon XP 32-bit laptop running Suse 10.1 using
2.6.16.13 kernel. Opteron machines running kernel 2.6.18 on Ubuntu
(compiled using gcc 4.1), Fedora Core 6, and Suse 10.1 will end with
subsets of the following errors:
semantic error: no match for probe point
while: resolving probe point kernel.inline("context_switch")
semantic error: no match for probe point
while: resolving probe point scheduler.cpu_off
semantic error: no match for probe point
while: resolving probe point kernel.inline("finish_task_switch")
semantic error: no match for probe point
while: resolving probe point scheduler.cpu_on
semantic error: no match for probe point
while: resolving probe point kernel.inline("pull_task")
semantic error: no match for probe point
while: resolving probe point scheduler.migrate
semantic error: no match for probe point
while: resolving probe point kernel.inline("idle_balance")
semantic error: no match for probe point
while: resolving probe point scheduler.balance
I have seem "pull_task" being problematic in previous emails, but could
not find any workaround mentioned. Is there any workaround for these
unresolved probes? Thanks.
Jason