From: "Frédéric Weisbecker" <fweisbec@gmail.com>
To: "Josh Boyer" <jwboyer@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
linuxppc-dev@ozlabs.org, Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH 0/2] ftrace: fixes for PPC
Date: Mon, 20 Oct 2008 19:42:38 +0200 [thread overview]
Message-ID: <c62985530810201042v4b3eed0ah62de285c64b2c0ba@mail.gmail.com> (raw)
In-Reply-To: <20081020170808.GB7249@yoda.jdub.homelinux.org>
2008/10/20 Josh Boyer <jwboyer@linux.vnet.ibm.com>:
> That seems like a good plan. Should we mark dynamic ftrace as X86 only
> in Kconfig for .28 to prevent people from inadvertently setting it?
Hi Josh.
There are other arch that support ftrace as well like sh or sparc64
(I'm currently working on
an implementation for mips).
So the choice would be better between waiting for a fix or disable
dynamic ftrace
on Kconfig only for PowerPC.
next prev parent reply other threads:[~2008-10-20 17:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-06 5:06 [PATCH 0/2] ftrace: fixes for PPC Steven Rostedt
2008-09-06 5:06 ` [PATCH 1/2] ftrace: use ftrace_release for all dynamic ftrace functions Steven Rostedt
2008-09-06 5:06 ` [PATCH 2/2] ftrace: fix unlocking of hash Steven Rostedt
2008-09-06 12:03 ` [PATCH 0/2] ftrace: fixes for PPC Ingo Molnar
2008-10-16 18:14 ` Josh Boyer
2008-10-16 18:22 ` Steven Rostedt
2008-10-16 18:35 ` Josh Boyer
2008-10-16 18:42 ` Steven Rostedt
2008-10-16 18:45 ` Steven Rostedt
2008-10-16 19:01 ` Josh Boyer
2008-10-20 16:30 ` Steven Rostedt
2008-10-20 17:08 ` Josh Boyer
2008-10-20 17:28 ` Steven Rostedt
2008-10-20 17:42 ` Frédéric Weisbecker [this message]
2008-10-20 17:53 ` Steven Rostedt
2008-10-20 21:47 ` Frédéric Weisbecker
2008-10-17 0:48 ` [PATCH] ftrace: powerpc: remove startup functions from tracing Steven Rostedt
2008-10-17 0:50 ` Benjamin Herrenschmidt
2008-10-17 1:04 ` Steven Rostedt
2008-10-17 5:37 ` [PATCH 0/2] ftrace: fixes for PPC Chris Friesen
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=c62985530810201042v4b3eed0ah62de285c64b2c0ba@mail.gmail.com \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).