From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8453 invoked by alias); 29 Sep 2009 00:57:38 -0000 Received: (qmail 8424 invoked by uid 9586); 29 Sep 2009 00:57:38 -0000 Date: Tue, 29 Sep 2009 00:57:00 -0000 Message-ID: <20090929005738.8413.qmail@sourceware.org> From: jistone@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.0-25-g55e50c2 X-Git-Refname: refs/heads/master X-Git-Reftype: branch X-Git-Oldrev: 5f8ca04fbb0682ff8647b4df5de68cd1042e312d X-Git-Newrev: 55e50c24c9176f1b3d15af94e145456a68e7ecf6 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-q3/txt/msg00329.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 55e50c24c9176f1b3d15af94e145456a68e7ecf6 (commit) from 5f8ca04fbb0682ff8647b4df5de68cd1042e312d (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 55e50c24c9176f1b3d15af94e145456a68e7ecf6 Author: Josh Stone Date: Mon Sep 28 17:36:04 2009 -0700 Try to build tracequery for all headers at once To mitigate PR10424, we switched to building a separate tracequery module for each tracepoint header, so a bad header wouldn't break all of the others. However, with recent kernels that leads to ~18 make commands, which adds up quickly in time. It's cached, so that's not too bad, but as a developer who rebuilds stap frequently, it gets annoying. If we're going to call 18 makes, it's worth it to start with one bigger make that covers all the headers at once (like we used to). If that one fails, we can still fall back to compiling individually. FWIW, the failing ext4.h header was only created in 2.6.31, and was fixed before 2.6.32, so the specific failure in PR10424 has a fairly small window. * buildrun.cxx (make_tracequery): Just take a single vector of headers. * hash.cxx (find_tracequery_hash): Deal with multiple headers. * tapsets.cxx (tracepoint_builder::get_tracequery_module): Ditto. (tracepoint_builder::init_dw): Attempt all system headers together, and if that fails, try again individually. ----------------------------------------------------------------------- Summary of changes: buildrun.cxx | 13 ++++--------- buildrun.h | 3 +-- hash.cxx | 7 ++++--- hash.h | 4 +++- tapsets.cxx | 58 +++++++++++++++++++++++++++++++++++++++++++--------------- 5 files changed, 55 insertions(+), 30 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool