From: Jiri Olsa <jolsa@redhat.com>
To: Zhou Chengming <zhouchengming1@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, acme@kernel.org,
rostedt@goodmis.org, jolsa@kernel.org,
linux-kernel@vger.kernel.org, huawei.libin@huawei.com
Subject: Re: [PATCH] perf/ftrace: fix doubled traces of perf on ftrace:function
Date: Mon, 28 Aug 2017 13:07:06 +0200 [thread overview]
Message-ID: <20170828110706.GA17767@krava> (raw)
In-Reply-To: <1503668977-12526-1-git-send-email-zhouchengming1@huawei.com>
On Fri, Aug 25, 2017 at 09:49:37PM +0800, Zhou Chengming wrote:
SNIP
> diff --git a/kernel/trace/trace_event_perf.c b/kernel/trace/trace_event_perf.c
> index 562fa69..70c5025 100644
> --- a/kernel/trace/trace_event_perf.c
> +++ b/kernel/trace/trace_event_perf.c
> @@ -306,6 +306,7 @@ void perf_trace_buf_update(void *record, u16 type)
> perf_ftrace_function_call(unsigned long ip, unsigned long parent_ip,
> struct ftrace_ops *ops, struct pt_regs *pt_regs)
> {
> + struct perf_event *event;
> struct ftrace_entry *entry;
> struct hlist_head *head;
> struct pt_regs regs;
> @@ -329,8 +330,9 @@ void perf_trace_buf_update(void *record, u16 type)
>
> entry->ip = ip;
> entry->parent_ip = parent_ip;
> + event = container_of(ops, struct perf_event, ftrace_ops);
nit, white space at the end of the line ^^^
but the change looks good to me
Reviewed-by: Jiri Olsa <jolsa@kernel.org>
thanks,
jirka
next prev parent reply other threads:[~2017-08-28 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 13:49 [PATCH] perf/ftrace: fix doubled traces of perf on ftrace:function Zhou Chengming
2017-08-25 13:56 ` Steven Rostedt
2017-08-28 11:07 ` Jiri Olsa [this message]
2017-08-29 13:06 ` [tip:perf/urgent] perf/ftrace: Fix double " tip-bot for Zhou Chengming
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=20170828110706.GA17767@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=huawei.libin@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=zhouchengming1@huawei.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox