From: Michael Ellerman <michael@ellerman.id.au>
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>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] powerpc, ftrace: use create_branch lib function
Date: Sun, 15 Feb 2009 00:49:26 +1100 [thread overview]
Message-ID: <1234619366.10265.3.camel@localhost> (raw)
In-Reply-To: <20090213150147.180922180@goodmis.org>
[-- Attachment #1: Type: text/plain, Size: 2146 bytes --]
On Fri, 2009-02-13 at 10:00 -0500, Steven Rostedt wrote:
> plain text document attachment
> (0002-powerpc-ftrace-use-create_branch-lib-function.patch)
> From: Steven Rostedt <srostedt@redhat.com>
>
> Impact: clean up, remove duplicate code
>
> When ftrace was first ported to PowerPC, there existed a
> create_function_call that would create the instruction to make a call
> to a given address. Unfortunately, this call expected to write to
> the address it was given, and since it used the address to calculate
> the offset, it could not be faked.
>
> ftrace needed a way to create the instruction without actually writing
> that instruction to the text section. So ftrace had to implement its
> own code.
>
> Now we have create_branch in the code patching library, which does
> exactly what ftrace needs. This patch replaces ftrace's implementation
> with the library function.
Thanks for doing this, I was going to once the ftrace code had settled a
little but you beat me to it.
> @@ -46,17 +41,10 @@ ftrace_call_replace(unsigned long ip, unsigned long addr, int link)
> {
> unsigned int op;
>
> - /*
> - * It would be nice to just use create_function_call, but that will
> - * update the code itself. Here we need to just return the
> - * instruction that is going to be modified, without modifying the
> - * code.
> - */
> addr = GET_ADDR(addr);
>
> /* if (link) set op to 'bl' else 'b' */
> - op = 0x48000000 | (link ? 1 : 0);
> - op |= (ftrace_calc_offset(ip, addr) & 0x03fffffc);
> + op = create_branch((unsigned int *)ip, addr, link ? 1 : 0);
If I was feeling nit-picky I'd say you should use:
op = create_branch((unsigned int *)ip, addr, link ? BRANCH_SET_LINK : 0);
But admittedly we're unlikely to ever change the flag handling, so it's
probably not worth the effort of a respin (or this email :).
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-14 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 15:00 [PATCH 0/2] [git-pull] powerpc, ftrace clean ups Steven Rostedt
2009-02-13 15:00 ` [PATCH 1/2] powerpc, ftrace: use unsigned int for instruction manipulation Steven Rostedt
2009-02-13 15:00 ` [PATCH 2/2] powerpc, ftrace: use create_branch lib function Steven Rostedt
2009-02-14 13:49 ` Michael Ellerman [this message]
2009-02-14 15:20 ` 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=1234619366.10265.3.camel@localhost \
--to=michael@ellerman.id.au \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--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).