From: Steven Rostedt <rostedt@goodmis.org>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 2/2] powerpc: ftrace_64: split further based on -mprofile-kernel
Date: Mon, 27 Feb 2017 10:40:14 -0500 [thread overview]
Message-ID: <20170227104014.7b7dee0e@gandalf.local.home> (raw)
In-Reply-To: <378311b965ca33fe69b159f7609ff2eedfe3bc2f.1487702678.git.naveen.n.rao@linux.vnet.ibm.com>
On Wed, 22 Feb 2017 00:31:02 +0530
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> wrote:
> Split ftrace_64.S further retaining the core ftrace 64-bit aspects
> in ftrace_64.S and moving ftrace_caller() and ftrace_graph_caller() into
> separate files based on -mprofile-kernel. The livepatch routines are all
> now contained within the mprofile file.
Why? I would think that it may be possible to share code if they stay
in the same file. I haven't had the chance to look deeply into the
current code, but there may be ways to make macros and consolidate
duplicate code like we did in x86.
-- Steve
>
> Signed-off-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
next prev parent reply other threads:[~2017-02-27 15:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 19:01 [PATCH v3 0/2] powerpc: split ftrace bits into separate files Naveen N. Rao
2017-02-21 19:01 ` [PATCH v3 1/2] powerpc: split ftrace bits into a separate file Naveen N. Rao
2017-02-27 15:36 ` Steven Rostedt
2017-02-28 4:04 ` Michael Ellerman
2017-02-28 14:11 ` Steven Rostedt
2017-03-01 15:23 ` Naveen N. Rao
2017-03-02 9:38 ` Michael Ellerman
2017-03-10 15:08 ` Naveen N. Rao
2017-03-10 15:45 ` Steven Rostedt
2017-03-10 16:08 ` Naveen N. Rao
2017-03-10 16:54 ` Steven Rostedt
2017-03-15 9:05 ` Naveen N. Rao
2017-03-15 13:11 ` Steven Rostedt
2017-03-15 13:57 ` Naveen N. Rao
2017-02-21 19:01 ` [PATCH v3 2/2] powerpc: ftrace_64: split further based on -mprofile-kernel Naveen N. Rao
2017-02-27 15:40 ` Steven Rostedt [this message]
2017-02-28 3:58 ` Michael Ellerman
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=20170227104014.7b7dee0e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.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