From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 824 invoked by alias); 10 Mar 2009 02:35:05 -0000 Received: (qmail 800 invoked by uid 9586); 10 Mar 2009 02:35:04 -0000 Date: Tue, 10 Mar 2009 02:35:00 -0000 Message-ID: <20090310023504.789.qmail@sourceware.org> From: jistone@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.9-95-ge0a1741 X-Git-Refname: refs/heads/master X-Git-Reftype: branch X-Git-Oldrev: d82227a838a0ac11827a4047dc33b9e38eefc3b7 X-Git-Newrev: e0a17418b9d12e2a95dc345e95080ba31a41677f Mailing-List: contact systemtap-cvs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-cvs-owner@sourceware.org List-Archive: Reply-To: systemtap@sourceware.org X-SW-Source: 2009-q1/txt/msg00245.txt.bz2 This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "systemtap: system-wide probe/trace tool". The branch, master has been updated via e0a17418b9d12e2a95dc345e95080ba31a41677f (commit) via be184deb8fa8f58ebe693c2483b9012daff6137d (commit) from d82227a838a0ac11827a4047dc33b9e38eefc3b7 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit e0a17418b9d12e2a95dc345e95080ba31a41677f Author: Josh Stone Date: Mon Mar 9 19:12:02 2009 -0700 Let -DINTERRUPTIBLE=0 mask interrupts in probes Some time ago we loosened up the code for all probe types to allow interrupts during the handler. However, when probing something like kernel.trace("*"), you get a mix of probes in and out of the interrupt path, and it becomes much more common to have probes skipped due to interrupt reentrancy. The common_probe_entryfn_prologue and common_probe_entryfn_epilogue functions had an interruptible flag, but this was no longer used anywhere. I removed this flag, but then reused the logic to check an INTERRUPTIBLE macro instead. Now users can use -DINTERRUPTIBLE=0 to prevent interrupt reentrancy in their script, at the cost of a bit more overhead to toggle the interrupt mask. commit be184deb8fa8f58ebe693c2483b9012daff6137d Author: Josh Stone Date: Mon Mar 9 19:10:20 2009 -0700 Fix a few typos in stap(1) ----------------------------------------------------------------------- Summary of changes: stap.1.in | 24 ++++++++++++++++++------ tapsets.cxx | 51 +++++++++++++++++++++++++++------------------------ translate.cxx | 3 +++ 3 files changed, 48 insertions(+), 30 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool