From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13764 invoked by alias); 21 May 2007 21:36:09 -0000 Received: (qmail 13755 invoked by uid 22791); 21 May 2007 21:36:09 -0000 X-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 21 May 2007 21:36:05 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l4LLa2SR006522; Mon, 21 May 2007 17:36:02 -0400 Received: from pobox.toronto.redhat.com (pobox.toronto.redhat.com [172.16.14.4]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l4LLa1bI031021; Mon, 21 May 2007 17:36:01 -0400 Received: from touchme.toronto.redhat.com (IDENT:postfix@touchme.toronto.redhat.com [172.16.14.9]) by pobox.toronto.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id l4LLa1BN009686; Mon, 21 May 2007 17:36:01 -0400 Received: from ton.toronto.redhat.com (ton.toronto.redhat.com [172.16.14.15]) by touchme.toronto.redhat.com (Postfix) with ESMTP id A6D79800087; Mon, 21 May 2007 17:36:00 -0400 (EDT) Received: from ton.toronto.redhat.com (localhost.localdomain [127.0.0.1]) by ton.toronto.redhat.com (8.13.1/8.13.1) with ESMTP id l4LLa0tP008981; Mon, 21 May 2007 17:36:00 -0400 Message-Id: <200705212136.l4LLa0tP008981@ton.toronto.redhat.com> To: Nathan DeBardeleben Cc: systemtap@sources.redhat.com Subject: Re: scheduler.stp scheduler.migrate having problems on 2.6.20-1 References: <465208BE.6080302@lanl.gov> Date: Mon, 21 May 2007 21:36:00 -0000 From: "Frank Ch. Eigler" Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2007-q2/txt/msg00352.txt.bz2 Nathan DeBardeleben writes: > While it seems to find the pull_task kernel function, I seem to be > unable to access the internal variables from that function. [...] Yes, yet another victim of bug #1155. > I'm looking to experiment with whether the kernel really is giving > processes the memory that is closest to which CPU it has chosen to > run a process on. Neat. You might try using a statement probe instead, choosing a source file:line somewhere near the beginning of the pull_task function. - FChE