From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>, Pekka Paalanen <pq@iki.fi>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 -tip 3/4] Tracing/ftrace: Adapt mmiotrace to the new type of print_line
Date: Tue, 30 Sep 2008 18:13:45 +0200 [thread overview]
Message-ID: <48E25039.8080907@gmail.com> (raw)
In-Reply-To: <20080930153912.GB22693@elte.hu>
Ingo Molnar wrote:
> * Frédéric Weisbecker <fweisbec@gmail.com> wrote:
>
>> 2008/9/30 Steven Rostedt <rostedt@goodmis.org>:
>>> OK, I'll nuke the ring_buffer_lock :-/
>>>
>>> The trace_pipe calls that and then calls print_trace_line which will
>>> eventually lock the buffer again. This is a bug on my part. I'll fix that
>>> today.
>>>
>>> Thanks,
>> Strange, I can't see any case where print_trace_line could call the
>> ring_buffer_lock.
>> Hmm, I will see in your patch.
>>
>> Ingo, I just saw one damage from the merging, trace_empty() returns
>> TRACE_TYPE_HANDLED. The type is wrong, it should return 1. It's not
>> urgent since the value is the same. Should I send a patch for such a
>> small error?
>
> yes, please do. One too many patch is far better than one too few ;-)
>
> Ingo
>
:)
Here it is!
Subject: [PATCH -tip] Tracing/ftrace: correct return value of trace_empty
Correct the value's type of trace_empty function
Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
---
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index 6a1c76b..da3789d 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -1686,7 +1686,7 @@ static int trace_empty(struct trace_iterator *iter)
if (!ring_buffer_iter_empty(iter->buffer_iter[cpu]))
return 0;
}
- return TRACE_TYPE_HANDLED;
+ return 1;
}
static enum print_line_t print_trace_line(struct trace_iterator *iter)
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index 6a1c76b..da3789d 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -1686,7 +1686,7 @@ static int trace_empty(struct trace_iterator *iter)
if (!ring_buffer_iter_empty(iter->buffer_iter[cpu]))
return 0;
}
- return TRACE_TYPE_HANDLED;
+ return 1;
}
static enum print_line_t print_trace_line(struct trace_iterator *iter)
next prev parent reply other threads:[~2008-09-30 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 18:27 [PATCH V2 -tip 3/4] Tracing/ftrace: Adapt mmiotrace to the new type of print_line Frederic Weisbecker
2008-09-29 19:19 ` Pekka Paalanen
2008-09-30 8:52 ` Ingo Molnar
2008-09-30 12:39 ` Frédéric Weisbecker
2008-09-30 12:45 ` Steven Rostedt
2008-09-30 13:25 ` Frédéric Weisbecker
2008-09-30 13:33 ` Steven Rostedt
2008-09-30 15:39 ` Ingo Molnar
2008-09-30 16:13 ` Frederic Weisbecker [this message]
2008-09-30 16:16 ` Frédéric Weisbecker
2008-10-01 8:06 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48E25039.8080907@gmail.com \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pq@iki.fi \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.