From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753019AbbDAQgq (ORCPT ); Wed, 1 Apr 2015 12:36:46 -0400 Received: from mail.kernel.org ([198.145.29.136]:40414 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751847AbbDAQgp (ORCPT ); Wed, 1 Apr 2015 12:36:45 -0400 From: Arnaldo Carvalho de Melo To: Jiri Olsa Cc: linux-kernel@vger.kernel.org, Arnaldo Carvalho de Melo , David Ahern , Adrian Hunter , Borislav Petkov , Don Zickus , Frederic Weisbecker , Namhyung Kim , Stephane Eranian Subject: [RFC 0/2] perf scripting cleanups Date: Wed, 1 Apr 2015 13:36:48 -0300 Message-Id: <1427906210-10519-1-git-send-email-acme@kernel.org> X-Mailer: git-send-email 1.9.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi David, Jiri, Please take a look if it is ok for you guys Adrian, there is another thing: db_export__sample(&tables->dbe, event, sample, evsel, al->thread, al); In tools/perf/util/scripting-engines/trace-event-python.c has this redundancy as well, see the (al->thread, al), I'll probably remove that extra thread parm there if you don't have any other subtle use for that... - Arnaldo Arnaldo Carvalho de Melo (2): perf script: No need to lookup thread twice perf scripting: No need to pass thread twice to the scripting callbacks tools/perf/builtin-script.c | 14 +++----------- tools/perf/util/scripting-engines/trace-event-perl.c | 5 ++--- tools/perf/util/scripting-engines/trace-event-python.c | 13 +++++-------- tools/perf/util/trace-event-scripting.c | 1 - tools/perf/util/trace-event.h | 3 +-- 5 files changed, 11 insertions(+), 25 deletions(-) -- 1.9.3