From c7a06645413b9c7c637693ac13ef3e885fcde31a Mon Sep 17 00:00:00 2001 From: Pekka Paalanen Date: Sat, 3 Jan 2009 21:09:27 +0200 Subject: [PATCH] --- yaml --- r: 131473 b: refs/heads/master c: f9aa28adfc6a4b01268ebb6d88566cca8627905f h: refs/heads/master i: 131471: 833c7fcf36dbdabae7bc28bcd3094ba5790b2294 v: v3 --- [refs] | 2 +- trunk/Documentation/tracers/mmiotrace.txt | 6 ++---- 2 files changed, 3 insertions(+), 5 deletions(-) diff --git a/[refs] b/[refs] index e4ed4b6bebcb..57c9d9388e03 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 6bc5c366b1a45ca18fba6851f62db5743b3f6db5 +refs/heads/master: f9aa28adfc6a4b01268ebb6d88566cca8627905f diff --git a/trunk/Documentation/tracers/mmiotrace.txt b/trunk/Documentation/tracers/mmiotrace.txt index cde23b4a12a1..5731c67abc55 100644 --- a/trunk/Documentation/tracers/mmiotrace.txt +++ b/trunk/Documentation/tracers/mmiotrace.txt @@ -78,12 +78,10 @@ to view your kernel log and look for "mmiotrace has lost events" warning. If events were lost, the trace is incomplete. You should enlarge the buffers and try again. Buffers are enlarged by first seeing how large the current buffers are: -$ cat /debug/tracing/trace_entries +$ cat /debug/tracing/buffer_size_kb gives you a number. Approximately double this number and write it back, for instance: -$ echo 0 > /debug/tracing/tracing_enabled -$ echo 128000 > /debug/tracing/trace_entries -$ echo 1 > /debug/tracing/tracing_enabled +$ echo 128000 > /debug/tracing/buffer_size_kb Then start again from the top. If you are doing a trace for a driver project, e.g. Nouveau, you should also