summaryrefslogtreecommitdiff
path: root/perf
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2009-06-08 11:52:56 +0100
committerChris Wilson <chris@chris-wilson.co.uk>2009-06-08 11:52:56 +0100
commit39bac6edddb8913d07fb25f14f088967ca846a78 (patch)
treed057931359a9d4d2ee90eb4085eb52c07b3df736 /perf
parent34ccaeae2d3cf1b5bdd8b97581d6e70324494356 (diff)
[perf] Mention cairo-perf-trace early on in the README
Diffstat (limited to 'perf')
-rw-r--r--perf/README2
1 files changed, 1 insertions, 1 deletions
diff --git a/perf/README b/perf/README
index efd9e4097..abf0687d1 100644
--- a/perf/README
+++ b/perf/README
@@ -184,7 +184,7 @@ How to benchmark traces
-----------------------
Using cairo-trace you can record the exact sequence of graphic operations
made by an application and replay them later. These traces can then be
-used to benchmark the various backends and patches.
+used by cairo-perf-trace to benchmark the various backends and patches.
To record a trace:
$ cairo-trace --no-mark-dirty --no-callers $APPLICATION [$ARGV]