From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8655 invoked by alias); 23 Jun 2011 16:28:14 -0000 Received: (qmail 8642 invoked by uid 22791); 23 Jun 2011 16:28:13 -0000 X-SWARE-Spam-Status: No, hits=-6.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 23 Jun 2011 16:27:54 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p5NGRsqT015092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 23 Jun 2011 12:27:54 -0400 Received: from localhost (vpn1-5-79.ams2.redhat.com [10.36.5.79]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p5NGRrah015834; Thu, 23 Jun 2011 12:27:53 -0400 Date: Thu, 23 Jun 2011 16:28:00 -0000 From: "Richard W.M. Jones" To: Josh Stone Cc: systemtap@sourceware.org Subject: Re: Rapidly running systemtap causing hangs or oops Message-ID: <20110623162752.GK803@amd.home.annexia.org> References: <20110622230025.GG18438@amd.home.annexia.org> <4E028028.4010603@redhat.com> <20110623075126.GJ803@amd.home.annexia.org> <4E0366B6.5020706@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E0366B6.5020706@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes 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: 2011-q2/txt/msg00325.txt.bz2 On Thu, Jun 23, 2011 at 09:15:50AM -0700, Josh Stone wrote: > On 06/23/2011 12:51 AM, Richard W.M. Jones wrote: > > Unfortunately for the real program I'm writing, I really do need a way > > to box stap around each test. The problem I was having before was > > that there was quite a long delay between my test running and stap > > probes firing (or at least, seeing stap output). I need the stap > > output from one test to be clearly distinct from the stap output from > > the next test. If there was a way to run the test and then say to > > stap "now flush all your output" before running the next test, then > > that would be acceptable. > > > > I thought about using the process ID, but ideally my tests will all > > run as the same pid. > > How about marking it with some other event that always and only happens > at the beginning or end of your test loop? e.g. take a mount: > > probe syscall.mount { > printf("Starting to mount %s on %s\n", source, target) > } Something like this could work, but timestamps seem to be working rather well now. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org