From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751927AbdFHWvl (ORCPT ); Thu, 8 Jun 2017 18:51:41 -0400 Received: from terminus.zytor.com ([65.50.211.136]:39877 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751528AbdFHWv3 (ORCPT ); Thu, 8 Jun 2017 18:51:29 -0400 Date: Thu, 8 Jun 2017 15:47:23 -0700 From: tip-bot for SeongJae Park Message-ID: Cc: sj38.park@gmail.com, tglx@linutronix.de, hpa@zytor.com, mingo@kernel.org, acme@redhat.com, fweisbec@gmail.com, peterz@infradead.org, alexander.shishkin@linux.intel.com, linux-kernel@vger.kernel.org, tzanussi@gmail.com Reply-To: linux-kernel@vger.kernel.org, tzanussi@gmail.com, alexander.shishkin@linux.intel.com, peterz@infradead.org, fweisbec@gmail.com, acme@redhat.com, mingo@kernel.org, hpa@zytor.com, tglx@linutronix.de, sj38.park@gmail.com In-Reply-To: <20170530111827.21732-3-sj38.park@gmail.com> References: <20170530111827.21732-3-sj38.park@gmail.com> To: linux-tip-commits@vger.kernel.org Subject: [tip:perf/urgent] perf script: Fix documentation errors Git-Commit-ID: 34d4453dac257be53c21abf2f713c992fb692b5c X-Mailer: tip-git-log-daemon Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Commit-ID: 34d4453dac257be53c21abf2f713c992fb692b5c Gitweb: http://git.kernel.org/tip/34d4453dac257be53c21abf2f713c992fb692b5c Author: SeongJae Park AuthorDate: Tue, 30 May 2017 20:18:24 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 7 Jun 2017 20:27:20 -0300 perf script: Fix documentation errors This commit fixes two errors in documents for perf-script-python and perf-script-perl as below: - /sys/kernel/debug/tracing events -> /sys/kernel/debug/tracing/events/ - trace_handled -> trace_unhandled Signed-off-by: SeongJae Park Cc: Alexander Shishkin Cc: Frederic Weisbecker Cc: Peter Zijlstra Cc: Tom Zanussi Fixes: cff68e582237 ("perf/scripts: Add perf-trace-python Documentation") Link: http://lkml.kernel.org/r/20170530111827.21732-3-sj38.park@gmail.com Signed-off-by: Arnaldo Carvalho de Melo --- tools/perf/Documentation/perf-script-perl.txt | 2 +- tools/perf/Documentation/perf-script-python.txt | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/tools/perf/Documentation/perf-script-perl.txt b/tools/perf/Documentation/perf-script-perl.txt index dfbb506..142606c 100644 --- a/tools/perf/Documentation/perf-script-perl.txt +++ b/tools/perf/Documentation/perf-script-perl.txt @@ -39,7 +39,7 @@ EVENT HANDLERS When perf script is invoked using a trace script, a user-defined 'handler function' is called for each event in the trace. If there's no handler function defined for a given event type, the event is -ignored (or passed to a 'trace_handled' function, see below) and the +ignored (or passed to a 'trace_unhandled' function, see below) and the next event is processed. Most of the event's field values are passed as arguments to the diff --git a/tools/perf/Documentation/perf-script-python.txt b/tools/perf/Documentation/perf-script-python.txt index 54acba2..087b87c9 100644 --- a/tools/perf/Documentation/perf-script-python.txt +++ b/tools/perf/Documentation/perf-script-python.txt @@ -321,7 +321,7 @@ So those are the essential steps in writing and running a script. The process can be generalized to any tracepoint or set of tracepoints you're interested in - basically find the tracepoint(s) you're interested in by looking at the list of available events shown by -'perf list' and/or look in /sys/kernel/debug/tracing events for +'perf list' and/or look in /sys/kernel/debug/tracing/events/ for detailed event and field info, record the corresponding trace data using 'perf record', passing it the list of interesting events, generate a skeleton script using 'perf script -g python' and modify the @@ -437,7 +437,7 @@ EVENT HANDLERS When perf script is invoked using a trace script, a user-defined 'handler function' is called for each event in the trace. If there's no handler function defined for a given event type, the event is -ignored (or passed to a 'trace_handled' function, see below) and the +ignored (or passed to a 'trace_unhandled' function, see below) and the next event is processed. Most of the event's field values are passed as arguments to the