lkml.org 
[lkml]   [2008]   [Sep]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Patch -tip 3/3] Tracing/ftrace: Don't consume entries unhandled by mmiotrace
On Thu, 25 Sep 2008 13:28:56 +0100
Frédéric Weisbecker <fweisbec@gmail.com> wrote:

> When mmiotrace can't handle an entry output, it returns 1.
> It should return 0 to relay on other output functions.
>
> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> ---
> diff --git a/kernel/trace/trace_mmiotrace.c b/kernel/trace/trace_mmiotrace.c
> index a108c32..6fe1315 100644
> --- a/kernel/trace/trace_mmiotrace.c
> +++ b/kernel/trace/trace_mmiotrace.c
> @@ -277,7 +277,8 @@ static int mmio_print_line(struct trace_iterator *iter)
> case TRACE_PRINT:
> return mmio_print_mark(iter);
> default:
> - return 1; /* ignore unknown entries */
> + return 0; /* ignore unknown entries whithout consuming */
> }
> }

NACK.

mmiotrace's log output is stricly specified, the standard/default
printing functions may NOT be used. The output is supposed to be
machine readable in addition to human readable.

The ftrace infrastructure assumes there is only one active tracer
at a time, therefore destroying unhandled entries is not a problem.

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

\
 
 \ /
  Last update: 2008-09-25 16:39    [W:1.590 / U:0.128 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site