[PATCH] doc: trace: Fix documentation for uprobe_profile

* [PATCH] doc: trace: Fix documentation for uprobe_profile
@ 2019-02-19  6:19 Srikar Dronamraju
  2019-02-21 15:29 ` Steven Rostedt
  0 siblings, 1 reply; 2+ messages in thread
From: Srikar Dronamraju @ 2019-02-19  6:19 UTC (permalink / raw)
  To: LKML
  Cc: Ingo Molnar, KAUSTUBH RAJENDRA WELANKAR, Srikar Dronamraju,
	Masami Hiramatsu, Steven Rostedt

uprobe_profile has filename and number of probe hits information for
each uprobe event. The documentation erroneously talks about probe
mis-hits. Update the documentation to the correct information.

Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
Reported-by: KAUSTUBH RAJENDRA WELANKAR <f20160095@hyderabad.bits-pilani.ac.in>
Signed-off-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
---
 Documentation/trace/uprobetracer.rst | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/Documentation/trace/uprobetracer.rst b/Documentation/trace/uprobetracer.rst
index 4c3bfde2..4346e23 100644
--- a/Documentation/trace/uprobetracer.rst
+++ b/Documentation/trace/uprobetracer.rst
@@ -73,10 +73,9 @@ For $comm, the default type is "string"; any other type is invalid.
 
 Event Profiling
 ---------------
-You can check the total number of probe hits and probe miss-hits via
-/sys/kernel/debug/tracing/uprobe_profile.
-The first column is event name, the second is the number of probe hits,
-the third is the number of probe miss-hits.
+You can check the total number of probe hits per event via
+/sys/kernel/debug/tracing/uprobe_profile. The first column is the filename,
+the second is the event name, the third is the number of probe hits.
 
 Usage examples
 --------------
-- 
2.7.4


^ permalink raw reply related	[flat|nested] 2+ messages in thread