[tip:perf/urgent] perf intel-pt: Remove no_force_psb from documentation

From: tip-bot for Adrian Hunter
Date: Sat Sep 26 2015 - 02:22:11 EST

Commit-ID: 597ee40722bf05195f91a41e88e15b79bdab152c
Gitweb: http://git.kernel.org/tip/597ee40722bf05195f91a41e88e15b79bdab152c
Author: Adrian Hunter <adrian.hunter@xxxxxxxxx>
AuthorDate: Thu, 24 Sep 2015 13:05:21 +0300
Committer: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
CommitDate: Fri, 25 Sep 2015 10:42:38 -0300

perf intel-pt: Remove no_force_psb from documentation

no_force_psb was dropped as a late change to the kernel driver.
Consequently, remove it from the documentation.

Signed-off-by: Adrian Hunter <adrian.hunter@xxxxxxxxx>
Cc: Jiri Olsa <jolsa@xxxxxxxxxx>
Link: http://lkml.kernel.org/r/1443089122-19082-2-git-send-email-adrian.hunter@xxxxxxxxx
Signed-off-by: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
tools/perf/Documentation/intel-pt.txt | 15 ---------------
1 file changed, 15 deletions(-)

diff --git a/tools/perf/Documentation/intel-pt.txt b/tools/perf/Documentation/intel-pt.txt
index 4a0501d..c94c9de 100644
--- a/tools/perf/Documentation/intel-pt.txt
+++ b/tools/perf/Documentation/intel-pt.txt
@@ -364,21 +364,6 @@ cyc_thresh Specifies how frequently CYC packets are produced - see cyc

CYC packets are not requested by default.

-no_force_psb This is a driver option and is not in the IA32_RTIT_CTL MSR.
- It stops the driver resetting the byte count to zero whenever
- enabling the trace (for example on context switches) which in
- turn results in no PSB being forced. However some processors
- will produce a PSB anyway.
- In any case, there is still a PSB when the trace is enabled for
- the first time.
- no_force_psb can be used to slightly decrease the trace size but
- may make it harder for the decoder to recover from errors.
- no_force_psb is not selected by default.

new snapshot option
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/