From: Tim Bird <tim.bird@am.sony.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux kernel <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 1/2] ftrace: Add duration filtering to function graph tracer
Date: Mon, 6 Jul 2009 19:22:13 -0700 [thread overview]
Message-ID: <4A52B155.2080000@am.sony.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0907062212370.8813@gandalf.stny.rr.com>
Steven Rostedt wrote:
> On Mon, 6 Jul 2009, Tim Bird wrote:
>> Another thing I thought of was to not commit the entry event until function
>> exit. I'm not sure the ring buffer supports having an entry outstanding for
>> long periods of time, though. This would, I believe, hold readers at the entries for
>> the last 'completed' functions, which might solve reader/writer races.
>
> Heh, I doubt that would be acceptable. The problem is that between reserve
> and commit, we disable preemption. Thus every function (even the scheduler
> itself) would have preemption disabled ;-)
Doh! I think I saw that, but only had a vague recollection of it.
Yeah, that would be a problem ;-)
I'll give the issues some more thought, and see if I can come
up with something.
Thanks for the feedback.
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================
prev parent reply other threads:[~2009-07-07 2:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 23:23 [PATCH 1/2] ftrace: Add duration filtering to function graph tracer Tim Bird
2009-07-07 0:22 ` Steven Rostedt
2009-07-07 1:39 ` Tim Bird
2009-07-07 2:15 ` Steven Rostedt
2009-07-07 2:22 ` Tim Bird [this message]
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=4A52B155.2080000@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox