From: "Helight.Xu" <helight.xu@gmail.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH V2] fix a warning on kernel/trace/trace_branch.c and trace_hw_branches.c
Date: Wed, 07 Oct 2009 19:40:37 +0800 [thread overview]
Message-ID: <4ACC7E35.4050001@gmail.com> (raw)
In-Reply-To: <4ACC5715.4000201@cn.fujitsu.com>
Li Zefan wrote:
> Zhenwen Xu wrote:
>
>> fix warnings that caused the API change of trace_buffer_lock_reserve()
>> change files: kernel/trace/trace_hw_branch.c
>> kernel/trace/trace_branch.c
>>
>>
>
> Hmm, did you really compile trace_hw_branch.c while testing
> this patch?
>
> This change is necessary too:
>
> - trace_buffer_unlock_commit(tr, event, 0, 0);
> + trace_buffer_unlock_commit(tr->buffer, event, 0, 0);
>
> And use a varaible "buffer = tr->buffer" should be better.
>
oh! sorry for my careless!
>
>> Signed-off-by: Zhenwen Xu <helight.xu@gmail.com>
>> ---
>> kernel/trace/trace_branch.c | 2 +-
>> kernel/trace/trace_hw_branches.c | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/kernel/trace/trace_branch.c b/kernel/trace/trace_branch.c
>> index 7a7a9fd..216e2dd 100644
>> --- a/kernel/trace/trace_branch.c
>> +++ b/kernel/trace/trace_branch.c
>> @@ -54,7 +54,7 @@ probe_likely_condition(struct ftrace_branch_data *f, int val, int expect)
>> goto out;
>>
>> pc = preempt_count();
>> - event = trace_buffer_lock_reserve(tr, TRACE_BRANCH,
>> + event = trace_buffer_lock_reserve(tr->buffer, TRACE_BRANCH,
>> sizeof(*entry), flags, pc);
>> if (!event)
>> goto out;
>> diff --git a/kernel/trace/trace_hw_branches.c b/kernel/trace/trace_hw_branches.c
>> index 23b6385..1cc17ca 100644
>> --- a/kernel/trace/trace_hw_branches.c
>> +++ b/kernel/trace/trace_hw_branches.c
>> @@ -180,7 +180,7 @@ void trace_hw_branch(u64 from, u64 to)
>> if (atomic_inc_return(&tr->data[cpu]->disabled) != 1)
>> goto out;
>>
>> - event = trace_buffer_lock_reserve(tr, TRACE_HW_BRANCHES,
>> + event = trace_buffer_lock_reserve(tr->buffer, TRACE_HW_BRANCHES,
>> sizeof(*entry), 0, 0);
>> if (!event)
>> goto out;
>>
>
>
--
---------------------------------
Zhenwen Xu - Open and Free
Home Page: http://zhwen.org
next prev parent reply other threads:[~2009-10-07 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 8:19 [PATCH V2] fix a warning on kernel/trace/trace_branch.c and trace_hw_branches.c Zhenwen Xu
2009-10-07 8:53 ` Li Zefan
2009-10-07 11:40 ` Helight.Xu [this message]
2009-10-07 13:46 ` Steven Rostedt
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=4ACC7E35.4050001@gmail.com \
--to=helight.xu@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@redhat.com \
--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.