[lkml]   [2009]   [Jan]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Patch in this message
    Subject[PATCH 1/3] doc: mmiotrace.txt, buffer size control change
    From: Pekka Paalanen <>

    Impact: prevents confusing the user when buffer size is inadequate

    The tracing framework offers a resizeable buffer, which mmiotrace uses
    to record events. If the buffer is full, the following events will be
    lost. Events should not be lost, so the documentation instructs the user
    to increase the buffer size. The buffer size is set via a debugfs file.

    Mmiotrace documentation was not updated the same time the debugfs file
    was changed. The old file was tracing/trace_entries and first contained
    the number of entries the buffer had space for, per cpu. Nowadays this
    file is replaced with the file tracing/buffer_size_kb, which tells the
    amount of memory reserved for the buffer, per cpu, in kilobytes.

    Previously, a flag had to be toggled via the debugfs file
    tracing/tracing_enabled when the buffer size was changed. This is no
    longer necessary.

    The mmiotrace documentation is updated to reflect the current state of
    the tracing framework.

    Signed-off-by: Pekka Paalanen <>
    Signed-off-by: Steven Rostedt <>
    Documentation/tracers/mmiotrace.txt | 6 ++----
    1 files changed, 2 insertions(+), 4 deletions(-)

    diff --git a/Documentation/tracers/mmiotrace.txt b/Documentation/tracers/mmiotrace.txt
    index cde23b4..5731c67 100644
    --- a/Documentation/tracers/mmiotrace.txt
    +++ b/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
    -$ cat /debug/tracing/trace_entries
    +$ cat /debug/tracing/buffer_size_kb
    gives you a number. Approximately double this number and write it back, for
    -$ 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

     \ /
      Last update: 2009-01-09 01:31    [W:0.021 / U:1.908 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site