From: Torsten Duwe <duwe@lst.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
ppc-dev <linuxppc-dev@lists.ozlabs.org>,
Jiri Kosina <jkosina@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] ppc64 ftrace implementation
Date: Mon, 8 Jun 2015 17:57:01 +0200 [thread overview]
Message-ID: <20150608155701.GA23784@lst.de> (raw)
In-Reply-To: <20150608113032.07544ece@gandalf.local.home>
On Mon, Jun 08, 2015 at 11:30:32AM -0400, Steven Rostedt wrote:
>
> Why are your patches all as replies?
Because I cared too much about the threading and the series that the
"Re:" escaped me.
> > Implement ftrace on ppc64
>
> What do you mean "Implement ftrace on ppc64"? It's already implemented.
Sorry, too deep in the details. It's DYNAMIC_FTRACE_WITH_REGS, actually.
Using gcc's -mprofile-kernel to call into ftrace...
> I'm not even going to bother looking at this patch because I have no
> idea what its purpose is.
Understandable ;-)
So: Implement DYNAMIC_FTRACE_WITH_REGS, in order to prepare for live patching.
Other obvious things I forgot to mention?
Torsten
next prev parent reply other threads:[~2015-06-08 15:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 16:11 [PATCH] ppc64 ftrace: mark data_access callees "notrace" (pt.1) Torsten Duwe
2015-05-15 1:34 ` Michael Ellerman
2015-05-15 8:45 ` Torsten Duwe
2015-05-16 8:05 ` Torsten Duwe
2015-05-18 12:29 ` Jiri Kosina
2015-05-19 3:27 ` Michael Ellerman
2015-05-19 9:52 ` Jiri Kosina
2015-06-03 13:02 ` [PATCH 0/4] ppc64 ftrace implementation Torsten Duwe
2015-06-03 13:08 ` [PATCH 1/4] " Torsten Duwe
2015-06-08 15:30 ` Steven Rostedt
2015-06-08 15:57 ` Torsten Duwe [this message]
2015-06-03 13:10 ` [PATCH 2/4] ppc64 ftrace configuration Torsten Duwe
2015-06-03 13:15 ` [PATCH 3/4] ppc64 ftrace: spare early boot and low level code Torsten Duwe
2015-06-03 13:22 ` [PATCH 4/4] ppc64 ftrace recursion protection Torsten Duwe
2015-05-20 9:03 ` [PATCH] ppc64 ftrace: mark data_access callees "notrace" (pt.1) Torsten Duwe
2015-05-26 14:34 ` Torsten Duwe
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=20150608155701.GA23784@lst.de \
--to=duwe@lst.de \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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).