From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23958 invoked by alias); 22 Jul 2014 14:50:32 -0000 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 Received: (qmail 23942 invoked by uid 89); 22 Jul 2014 14:50:32 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 22 Jul 2014 14:50:30 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s6MEoO5p027605 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 22 Jul 2014 10:50:24 -0400 Received: from t540p.usersys.redhat.com (vpn-54-16.rdu2.redhat.com [10.10.54.16]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s6MEoNTV031383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 22 Jul 2014 10:50:24 -0400 Message-ID: <53CE7A2E.6010306@redhat.com> Date: Tue, 22 Jul 2014 14:50:00 -0000 From: David Smith User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Nathan Scott CC: Systemtap List , pcp Subject: Re: [pcp] systemtap/pcp integration References: <53C83CB9.3020808@redhat.com> <861139755.14608867.1405992742567.JavaMail.zimbra@redhat.com> In-Reply-To: <861139755.14608867.1405992742567.JavaMail.zimbra@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014-q3/txt/msg00072.txt.bz2 On 07/21/2014 08:32 PM, Nathan Scott wrote: > Hi David, > > ----- Original Message ----- >> [...] >> Note that systemtap will create a file called 'mmv' in >> /proc/systemtap/{MODULE_NAME}. I've just been using pcp's 'mmvdump' >> utility to dump the contents of the /proc/systemtap/{MODULE_NAME}/mmv >> file. Currently the pcp mmv pmda only looks in one place for mmv files, >> but it might be possible to create a symbolic link to systemtap's mmv >> file to make it happy. > > (OOC, what's {MODULE_NAME} in this context?) As Frank mentioned, {MODULE_NAME} is the name of the module, usually autogenerated. > A symlink would sorta work but it feels like a bit of a workaround - the > PMDA is written to be able to detect arrival/departure of new MMV files > based on changes in a directory (and the location of that directory is > parameterised via /etc/pcp.conf variables). I'd not recommend trying to > find it within a stap script ... I imagine it will be cleaner if we go > for separate user/kernel locations for MMV files. The symlink feels like a bit of a workaround, because it *is* one. Long term we certainly want a better way to find the systemtap MMV files. > Attached patch (lightly tested) implements the PCP side of things with > that in mind - with this patch (and making the kernel code manage the > lifecycle of separate /proc/mmv/* entries), things should begin to work > out-of-the-box (the MMV PMDA is already default-enabled in the default > pmcd config file, so everything else is in place for you). This code sounds like a step in the right direction. Thanks. -- David Smith dsmith@redhat.com Red Hat http://www.redhat.com 256.217.0141 (direct) 256.837.0057 (fax)