From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
David Miller <davem@davemloft.net>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
Roland McGrath <roland@redhat.com>,
Ulrich Drepper <drepper@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Gregory Haskins <ghaskins@novell.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
"Luis Claudio R. Goncalves" <lclaudio@uudg.org>,
Clark Williams <williams@redhat.com>,
Bruce Duncan <bwduncan@gmail.com>,
Marcin Slusarz <marcin.slusarz@gmail.com>,
Steven Rostedt <srostedt@redhat.com>
Subject: Re: [PATCH v2 0/6] ftrace: to kill a daemon (small updates)
Date: Fri, 15 Aug 2008 11:24:12 +0200 [thread overview]
Message-ID: <20080815092412.GC22209@elte.hu> (raw)
In-Reply-To: <20080814194506.233473381@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> [
> Changes since v1:
>
> regex fix in x86_64 recordmcount.pl. Now it can handle all
> mcount+0x... mcount-0x... and mcount, where as the original
> only handled mcount+0x...
>
> Made mcount on start-up to simply return. The current mcount
> is set up to be replaced with a call to ftrace_record_ip.
> This is no longer necessary.
>
> Note: This patch series is focusing on how calls to mcount in
> the kernel are converted to nops. It does not address what
> kind of nop is used. That is a different topic, and should
> be in a different patch series.
>
> Note 2: I have found that the changes here are more stable than
> the current daemon method, and these patches should be used.
> It also solves the resume from suspend to ram bug that was
> reported:
>
> http://lkml.org/lkml/2008/8/12/234
> and
> http://lkml.org/lkml/2008/8/12/451
>
> Note 3: I have already ported this to PowerPC64, but I am waiting
> for this to be accepted first before submitting those changes.
> ]
>
> One of the things that bothered me about the latest ftrace code was
> this annoying daemon that would wake up once a second to see if it had
> work to do. If it did not, it would go to sleep, otherwise it would do
> its work and then go to sleep.
i like this concept alot - i've applied the whole lot to
tip/tracing/ftrace.
Eventually gcc should be extended to provide a separate section for
instrumentation patch sites, instead of us having to disassemble the
object code. That would also make the ftrace build faster. Any gcc folks
interested in that?
Ingo
next prev parent reply other threads:[~2008-08-15 9:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 19:45 [PATCH v2 0/6] ftrace: to kill a daemon (small updates) Steven Rostedt
2008-08-14 19:45 ` [PATCH v2 1/6] ftrace: create __mcount_loc section Steven Rostedt
2008-08-14 19:45 ` [PATCH v2 2/6] ftrace: mcount call site on boot nops core Steven Rostedt
2008-08-14 19:45 ` [PATCH v2 3/6] ftrace: enable mcount recording for modules Steven Rostedt
2008-08-14 23:26 ` Rusty Russell
2008-08-14 23:40 ` Steven Rostedt
2008-08-14 19:45 ` [PATCH v2 4/6] ftrace: rebuild everything on change to FTRACE_MCOUNT_RECORD Steven Rostedt
2008-08-14 19:45 ` [PATCH v2 5/6] ftrace: enable using mcount recording on x86 Steven Rostedt
2008-08-14 19:45 ` [PATCH v2 6/6] ftrace: x86 mcount stub Steven Rostedt
2008-08-15 9:24 ` Ingo Molnar [this message]
2008-08-15 11:22 ` [PATCH v2 0/6] ftrace: to kill a daemon (small updates) Gregory Haskins
2008-08-15 12:36 ` Marcin Slusarz
2008-08-15 12:50 ` Steven Rostedt
2008-08-15 13:35 ` Marcin Slusarz
2008-08-20 19:28 ` Marcin Slusarz
2008-08-20 19:36 ` Steven Rostedt
2008-08-21 12:08 ` Ingo Molnar
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=20080815092412.GC22209@elte.hu \
--to=mingo@elte.hu \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bwduncan@gmail.com \
--cc=davem@davemloft.net \
--cc=drepper@redhat.com \
--cc=ghaskins@novell.com \
--cc=jeremy@goop.org \
--cc=lclaudio@uudg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=peterz@infradead.org \
--cc=roland@redhat.com \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox