From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752790AbdKQRzR (ORCPT ); Fri, 17 Nov 2017 12:55:17 -0500 Received: from mail-wm0-f65.google.com ([74.125.82.65]:42366 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751124AbdKQRzK (ORCPT ); Fri, 17 Nov 2017 12:55:10 -0500 X-Google-Smtp-Source: AGs4zMZ62HUch3/TlDRDxcZ+GqduhNk3Ljpkjb9SjlMR0EdYoJSkaQXtJ4ZDuuQFEtS+0/g4M6ZqBA== From: "Vladislav Valtchev (VMware)" To: rostedt@goodmis.org, linux-kernel@vger.kernel.org Cc: y.karadz@gmail.com, "Vladislav Valtchev (VMware)" Subject: [PATCH] trace-cmd: s/plugin/tracer/ in record's man page Date: Fri, 17 Nov 2017 19:54:22 +0200 Message-Id: <20171117175422.3875-1-vladislav.valtchev@gmail.com> X-Mailer: git-send-email 2.14.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Currently, the man page of trace-cmd record states that: To see a list of available plugins, see trace-cmd-list(1). While `trace-cmd list` [w/o options] mentions "tracers", which is the proper term there. The inconsistency exists because the terminology in trace-cmd/ftrace changed over time: what we call today "tracers" use to be called "plugins" when ftrace was created. This simple patch updates trace-cmd record's man page accordingly, in order to avoid any confusion and improve the user experience. Signed-off-by: Vladislav Valtchev (VMware) --- Documentation/trace-cmd-record.1.txt | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/Documentation/trace-cmd-record.1.txt b/Documentation/trace-cmd-record.1.txt index 5663447..68afa16 100644 --- a/Documentation/trace-cmd-record.1.txt +++ b/Documentation/trace-cmd-record.1.txt @@ -25,12 +25,11 @@ file that can later be read (see trace-cmd-report(1)). OPTIONS ------- -*-p* 'plugin':: - Specify a trace plugin. Plugins are special Ftrace tracers that usually do - more than just trace an event. Common plugins are *function*, - *function_graph*, *preemptirqsoff*, *irqsoff*, *preemptoff*, and *wakeup*. - A plugin must be supported by the running kernel. To see a list of - available plugins, see trace-cmd-list(1). +*-p* 'tracer':: + Specify a tracer. Tracers usually do more than just trace an event. + Common tracers are: *function*, *function_graph*, *preemptirqsoff*, + *irqsoff*, *preemptoff* and *wakeup*. A tracer must be supported by the + running kernel. To see a list of available tracers, see trace-cmd-list(1). *-e* 'event':: Specify an event to trace. Various static trace points have been added to -- 2.14.1