From: Michael Neuling <mikey@neuling.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
Steven Rostedt <srostedt@redhat.com>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] powerpc, ftrace: fix compile error when modules not configured
Date: Fri, 06 Feb 2009 17:23:52 +1100 [thread overview]
Message-ID: <12951.1233901432@neuling.org> (raw)
In-Reply-To: <20090206060527.369616736@goodmis.org>
In message <20090206060527.369616736@goodmis.org> you wrote:
> From: Steven Rostedt <srostedt@redhat.com>
>
> Michael Neuling reported a compile bug when dynamic ftrace was
> configured in and modules were not. This was due to the ftrace
> code referencing module specific structures.
>
> Reported-by: Michael Neuling <mikey@neuling.org>
> Signed-off-by: Steven Rostedt <srostedt@redhat.com>
Steve,
Thanks, fixes the error I was seeing.
As an aside, is there anyway we can merge some of the code in
arch/powerpc/kernel/ftrace.c between 32 and 64bit? There seems to be a
lot of repeated code in there with only minor changes.
Mikey
> ---
> arch/powerpc/kernel/ftrace.c | 16 +++++++++++++++-
> 1 files changed, 15 insertions(+), 1 deletions(-)
>
> diff --git a/arch/powerpc/kernel/ftrace.c b/arch/powerpc/kernel/ftrace.c
> index a913f91..88c641d 100644
> --- a/arch/powerpc/kernel/ftrace.c
> +++ b/arch/powerpc/kernel/ftrace.c
> @@ -113,6 +113,8 @@ static int test_24bit_addr(unsigned long ip, unsigned lon
g addr)
> return create_branch((unsigned int *)ip, addr, 0);
> }
>
> +#ifdef CONFIG_MODULES
> +
> static int is_bl_op(unsigned int op)
> {
> return (op & 0xfc000003) == 0x48000001;
> @@ -323,6 +325,7 @@ __ftrace_make_nop(struct module *mod,
> return 0;
> }
> #endif /* PPC64 */
> +#endif /* CONFIG_MODULES */
>
> int ftrace_make_nop(struct module *mod,
> struct dyn_ftrace *rec, unsigned long addr)
> @@ -342,6 +345,7 @@ int ftrace_make_nop(struct module *mod,
> return ftrace_modify_code(ip, old, new);
> }
>
> +#ifdef CONFIG_MODULES
> /*
> * Out of range jumps are called from modules.
> * We should either already have a pointer to the module
> @@ -366,9 +370,13 @@ int ftrace_make_nop(struct module *mod,
> mod = rec->arch.mod;
>
> return __ftrace_make_nop(mod, rec, addr);
> -
> +#else
> + /* We should not get here without modules */
> + return -EINVAL;
> +#endif /* CONFIG_MODULES */
> }
>
> +#ifdef CONFIG_MODULES
> #ifdef CONFIG_PPC64
> static int
> __ftrace_make_call(struct dyn_ftrace *rec, unsigned long addr)
> @@ -457,6 +465,7 @@ __ftrace_make_call(struct dyn_ftrace *rec, unsigned long
addr)
> return 0;
> }
> #endif /* CONFIG_PPC64 */
> +#endif /* CONFIG_MODULES */
>
> int ftrace_make_call(struct dyn_ftrace *rec, unsigned long addr)
> {
> @@ -475,6 +484,7 @@ int ftrace_make_call(struct dyn_ftrace *rec, unsigned lon
g addr)
> return ftrace_modify_code(ip, old, new);
> }
>
> +#ifdef CONFIG_MODULES
> /*
> * Out of range jumps are called from modules.
> * Being that we are converting from nop, it had better
> @@ -486,6 +496,10 @@ int ftrace_make_call(struct dyn_ftrace *rec, unsigned lo
ng addr)
> }
>
> return __ftrace_make_call(rec, addr);
> +#else
> + /* We should not get here without modules */
> + return -EINVAL;
> +#endif /* CONFIG_MODULES */
> }
>
> int ftrace_update_ftrace_func(ftrace_func_t func)
> --
> 1.5.6.5
>
> --
>
next prev parent reply other threads:[~2009-02-06 6:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090206060328.181057235@goodmis.org>
[not found] ` <20090206060527.148611255@goodmis.org>
2009-02-06 6:07 ` [PATCH 1/2] ftrace, powerpc: replace debug macro with proper pr_deug Steven Rostedt
[not found] ` <20090206060527.369616736@goodmis.org>
2009-02-06 6:07 ` [PATCH 2/2] powerpc, ftrace: fix compile error when modules not configured Steven Rostedt
2009-02-06 6:23 ` Michael Neuling [this message]
2009-02-06 6:27 ` 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=12951.1233901432@neuling.org \
--to=mikey@neuling.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.org \
--cc=srostedt@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;
as well as URLs for NNTP newsgroup(s).