From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26756 invoked by alias); 12 Oct 2006 18:10:49 -0000 Received: (qmail 26747 invoked by uid 22791); 12 Oct 2006 18:10:47 -0000 X-Spam-Status: No, hits=1.5 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,FORGED_RCVD_HELO X-Spam-Check-By: sourceware.org Received: from outbound-ash.frontbridge.com (HELO outbound1-ash-R.bigfish.com) (206.16.192.249) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 12 Oct 2006 18:10:36 +0000 Received: from outbound1-ash.bigfish.com (localhost.localdomain [127.0.0.1]) by outbound1-ash-R.bigfish.com (Postfix) with ESMTP id C71EA17368EE for ; Thu, 12 Oct 2006 18:09:02 +0000 (UTC) Received: from mail22-ash-R.bigfish.com (unknown [172.18.2.3]) by outbound1-ash.bigfish.com (Postfix) with ESMTP id BFA701706EC7 for ; Thu, 12 Oct 2006 18:09:02 +0000 (UTC) Received: from mail22-ash.bigfish.com (localhost.localdomain [127.0.0.1]) by mail22-ash-R.bigfish.com (Postfix) with ESMTP id B3C626BC9A8 for ; Thu, 12 Oct 2006 18:09:02 +0000 (UTC) X-BigFish: VP Received: by mail22-ash (MessageSwitch) id 1160676542650196_31619; Thu, 12 Oct 2006 18:09:02 +0000 (UCT) Received: from amdext4.amd.com (amdext4.amd.com [163.181.251.6]) by mail22-ash.bigfish.com (Postfix) with ESMTP id 870FA6BC8AD for ; Thu, 12 Oct 2006 18:09:02 +0000 (UTC) Received: from SAUSGW01.amd.com (sausgw01.amd.com [163.181.250.21]) by amdext4.amd.com (8.12.11/8.12.11/AMD) with ESMTP id k9CI8an6003362 for ; Thu, 12 Oct 2006 13:09:01 -0500 Received: from 163.181.22.101 by SAUSGW02.amd.com with ESMTP (AMD SMTP Relay (Email Firewall v6.1.0)); Thu, 12 Oct 2006 13:08:55 -0500 X-Server-Uuid: 5FC0E2DF-CD44-48CD-883A-0ED95B391E89 Received: from sausexmb1.amd.com ([163.181.3.156]) by sausexbh1.amd.com with Microsoft SMTPSVC(6.0.3790.2499); Thu, 12 Oct 2006 13:08:54 -0500 Received: from [163.181.4.84] ([163.181.4.84]) by sausexmb1.amd.com with Microsoft SMTPSVC(6.0.3790.2499); Thu, 12 Oct 2006 13:08:55 -0500 Message-ID: <452E8704.1020105@amd.com> Date: Thu, 12 Oct 2006 18:10:00 -0000 From: "Jason Yeh" User-Agent: Thunderbird 1.5.0.5 (X11/20060728) MIME-Version: 1.0 To: systemtap@sources.redhat.com Subject: resolving probe point context_switch References: <20061012152411.GA3979@redhat.com> In-Reply-To: <20061012152411.GA3979@redhat.com> X-OriginalArrivalTime: 12 Oct 2006 18:08:55.0040 (UTC) FILETIME=[7AF23000:01C6EE29] X-WSS-ID: 69305B3D0Y46016724-01-01 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2006-q4/txt/msg00104.txt.bz2 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