From: Ingo Molnar <mingo@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@redhat.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
"zhangwei(Jovi)" <jovi.zhangwei@huawei.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 0/3] Teach perf_trace_##call() to check hlist_empty(perf_events)
Date: Fri, 19 Jul 2013 09:43:39 +0200 [thread overview]
Message-ID: <20130719074339.GA22597@gmail.com> (raw)
In-Reply-To: <20130718183018.GA4043@redhat.com>
* Oleg Nesterov <oleg@redhat.com> wrote:
> Hello.
>
> The patches are the same, I only tried to update the changelogs a bit.
> I am also quoting my old email below, to explain what this hack tries
> to do.
>
> Say, "perf record -e sched:sched_switch -p1".
>
> Every task except /sbin/init will do perf_trace_sched_switch() and
> perf_trace_buf_prepare() + perf_trace_buf_submit for no reason(),
> it doesn't have a counter.
>
> So it makes sense to add the fast-path check at the start of
> perf_trace_##call(),
>
> if (hlist_empty(event_call->perf_events))
> return;
>
> The problem is, we should not do this if __task != NULL (iow, if
> DECLARE_EVENT_CLASS() uses __perf_task()), perf_tp_event() has the
> additional code for this case.
>
> So we should do
>
> if (!__task && hlist_empty(event_call->perf_events))
> return;
>
> But __task is changed by "{ assign; }" block right before
> perf_trace_buf_submit(). Too late for the fast-path check,
> we already called perf_trace_buf_prepare/fetch_regs.
>
> So. After 2/3 __perf_task() (and __perf_count/addr) is called
> when ftrace_get_offsets_##call(args) evaluates the arguments,
> and we can check !__task && hlist_empty() right after that.
>
> Oleg.
Nice improvement.
Peter, Steve, any objections?
Thanks,
Ingo
next prev parent reply other threads:[~2013-07-19 7:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 18:30 [PATCH RESEND 0/3] Teach perf_trace_##call() to check hlist_empty(perf_events) Oleg Nesterov
2013-07-18 18:30 ` [PATCH 1/3] tracing/perf: expand TRACE_EVENT(sched_stat_runtime) Oleg Nesterov
2013-07-18 18:30 ` [PATCH 2/3] tracing/perf: reimplement TP_perf_assign() logic Oleg Nesterov
2013-07-18 18:30 ` [PATCH 3/3] tracing/perf: Avoid perf_trace_buf_*() in perf_trace_##call() when possible Oleg Nesterov
2013-07-19 7:43 ` Ingo Molnar [this message]
2013-07-19 20:27 ` [PATCH RESEND 0/3] Teach perf_trace_##call() to check hlist_empty(perf_events) Steven Rostedt
2013-07-19 21:00 ` David Ahern
2013-07-20 15:40 ` Oleg Nesterov
2013-07-26 15:20 ` Oleg Nesterov
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=20130719074339.GA22597@gmail.com \
--to=mingo@kernel.org \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jovi.zhangwei@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--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.