linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Paul Mackerras <paulus@samba.org>,
	linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/1] powerpc: make mcount a stub for dynamic ftrace
Date: Sun, 23 Nov 2008 13:49:58 +0100	[thread overview]
Message-ID: <20081123124958.GM29663@elte.hu> (raw)
In-Reply-To: <20081120215541.489725873@goodmis.org>


* Steven Rostedt <rostedt@goodmis.org> wrote:

> Paul,
> 
> I have one more patch. I added it to the end of the ppc/ftrace 
> branch. The new way of handling the finding of mcounts means we do 
> not need to do anything in the mcount call itself. It should just be 
> a stub and when ftrace is enabled, it will change the caller sites 
> to call something other than mcount.
> 
> The following patches are in:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> 
>     branch: ppc/ftrace

i've also pulled the ppc/ftrace branch into tip/tracing/powerpc, and 
added it to ftrace-next's linux-next integration rules.

So if Paul gives the green light that the commits have the right 
structure, we can freeze down the branch and the SHA1's and integrate 
it into ftrace-next. (which is integrated in linux-next after the 
powerpc tree so should be all fine in terms of merge ordering)

	Ingo

      parent reply	other threads:[~2008-11-23 12:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20 21:55 [PATCH 0/1] powerpc: make mcount a stub for dynamic ftrace Steven Rostedt
2008-11-20 21:55 ` [PATCH 1/1] powerpc: ftrace, do nothing in mcount call for dyn ftrace Steven Rostedt
2008-11-23 12:49 ` Ingo Molnar [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=20081123124958.GM29663@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).