All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis Claudio R. Goncalves" <lclaudio@uudg.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, williams <williams@redhat.com>,
	tglx <tglx@linutronix.de>
Subject: Re: [PATCH 0/9] Backport of ftrace's function profiler
Date: Tue, 19 May 2009 12:12:00 -0300	[thread overview]
Message-ID: <20090519151200.GR27687@unix.sh> (raw)
In-Reply-To: <alpine.DEB.2.00.0905191105530.7816@gandalf.stny.rr.com>

On Tue, May 19, 2009 at 11:06:55AM -0400, Steven Rostedt wrote:
| 
| On Tue, 19 May 2009, Luis Claudio R. Goncalves wrote:
| 
| > Hello,
| > 
| > The following patches are the backport of Steven Rostedt's ftrace's
| > function profiler, as published in his RFC series posted to LKML. This
| > backport has been done on top of 2.6.29.3-rt14.
| > 
| > The feature is fully functional but we do have one known problem, a kernel
| > panic when stressing the function profiler (a fast sequence of start, stop,
| > read in loop for 30+ minutes). This problem has a Bugzilla entry at:
| > 
| > 	https://bugzilla.redhat.com/show_bug.cgi?id=500156
| 
| Luis,
| 
| I'm fine with this, but if you want me to review the patches, it would 
| help if you have the reject files that you had to solve (or merge conflict 
| files). Then I can see if changes were made correctly.

So I finally found a use for those ugly reject files I always delete... :)

Steven, I will have to redo part of the work to get the reject files again.
Hopefully it won't take long. Thanks for being available to review the
backport!

Luis
-- 
[ Luis Claudio R. Goncalves             Red Hat  -  Realtime Team ]
[ Fingerprint: 4FDD B8C4 3C59 34BD 8BE9  2696 7203 D980 A448 C8F8 ]


  reply	other threads:[~2009-05-19 15:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 14:36 [PATCH 0/9] Backport of ftrace's function profiler Luis Claudio R. Goncalves
2009-05-19 14:43 ` [PATCH 1/9] tracing: add " Luis Claudio R. Goncalves
2009-05-19 14:45 ` [PATCH 2/9] reduce size of memory in " Luis Claudio R. Goncalves
2009-05-19 14:48 ` [PATCH 3/9] tracing: adding function timings to function profile Luis Claudio R. Goncalves
2009-05-19 14:52 ` [PATCH 4/9] tracing: make the function profiler per cpu Luis Claudio R. Goncalves
2009-05-19 14:55 ` [PATCH 5/9] function graph add option to calculate graph time off Luis Claudio R. Goncalves
2009-05-19 14:58 ` [PATCH 6/9] tracing: remove on the fly allocator from function profiler Luis Claudio R. Goncalves
2009-05-19 15:01 ` [PATCH 7/9] tracing: add average time in function to " Luis Claudio R. Goncalves
2009-05-19 15:03 ` [PATCH 8/9] backport function profiler fixes Luis Claudio R. Goncalves
2009-05-19 15:05 ` [PATCH 9/9] ftrace: function profiler band-aid Luis Claudio R. Goncalves
2009-05-19 15:06 ` [PATCH 0/9] Backport of ftrace's function profiler Steven Rostedt
2009-05-19 15:12   ` Luis Claudio R. Goncalves [this message]
2009-05-19 15:15     ` 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=20090519151200.GR27687@unix.sh \
    --to=lclaudio@uudg.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=williams@redhat.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 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.