From: Gregory Haskins <ghaskins@novell.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
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>,
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 07:22:52 -0400 [thread overview]
Message-ID: <48A5670C.2080805@novell.com> (raw)
In-Reply-To: <20080815092412.GC22209@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
(From the original mail)
Steven Rostedt wrote:
>
> Along came Gregory Haskins, who was bickering about having ftrace enabled
> on a production -rt kernel. I told him the reasons that this would be bad
> and then he started thinking out loud, and suggesting wild ideas, like
> patching gcc!
>
^^^^^^^^^^
Ingo Molnar wrote:
> Eventually gcc should be extended to provide a separate section for
> instrumentation patch sites, instead of us having to disassemble the
> object code.
:)
I obviously agree with this, so +1
Though, tbh, at the time I suggested it I didn't think of Steve's idea
to post-process which was quite clever. But I do agree that having gcc
do it will probably save some build time since it will probably be
trivial for it to do this when already processing -pg. It would have the
added benefit of letting the arch specific toolchain do the arch
specific work (though I think Steve's solution capitalizes on the
toolchain extensively as it is).
The biggest downside is that we would have an external dependency on gcc
for the feature, but I guess the kernel already has some of those anyway
(e.g. the stack overflow guard feature, etc). We could always fall back
on Steve's post-processing if the toolchain lacks the feature.
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2008-08-15 11:25 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 ` [PATCH v2 0/6] ftrace: to kill a daemon (small updates) Ingo Molnar
2008-08-15 11:22 ` Gregory Haskins [this message]
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=48A5670C.2080805@novell.com \
--to=ghaskins@novell.com \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bwduncan@gmail.com \
--cc=davem@davemloft.net \
--cc=drepper@redhat.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=mingo@elte.hu \
--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 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.