From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Namhyung Kim <namhyung.kim@lge.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [RFC/PATCH] ftrace: add set_graph_notrace filter
Date: Fri, 11 Oct 2013 10:58:09 +0200 [thread overview]
Message-ID: <20131011085809.GD4154@osiris> (raw)
In-Reply-To: <871u3scik4.fsf@sejong.aot.lge.com>
On Fri, Oct 11, 2013 at 05:34:19PM +0900, Namhyung Kim wrote:
> Hi Heiko,
>
> On Fri, 11 Oct 2013 09:21:56 +0200, Heiko Carstens wrote:
> > On Fri, Oct 11, 2013 at 12:17:17AM -0400, Steven Rostedt wrote:
> >> Isn't there a way we could pass the state? Hmm, I think we could use
> >> depth to do that. As depth is a pointer to trace.depth and not used
> >> before then. We could make it negative and then check that.
> >>
> >> /me looks at other archs.
> >>
> >> Darn it, s390 calls ftrace_push_return_trace() before
> >> ftrace_graph_entry(). They got fancy, as they must have noticed that
> >> trace.depth is set by ftrace_push_return_trace() and they just figured
> >> to let the ftrace_push_return_trace() do the work.
> >>
> >> Hmm, we could add a config to do the check on one side or the other
> >> depending on how the arch handles it.
> >>
> >> It needs to be well commented though.
> >
> > I don't remember I why decided to do that more than four years ago, however
> > on the other hand I really don't think we need a config for this.
> > So I just committed the patch below... it compiles and doesn't crash
> > immediately, so must be good.
> > It will be merged during the next merge window.
>
> Nice!
>
> >
> > From 8c539d10400ee2efe000d324497a0661a2143dbf Mon Sep 17 00:00:00 2001
> > From: Heiko Carstens <heiko.carstens@de.ibm.com>
> > Date: Fri, 11 Oct 2013 08:55:57 +0200
> > Subject: [PATCH] s390/ftrace: prepare_ftrace_return() function call order
> >
> > Steven Rostedt noted that s390 is the only architecture which calls
> > ftrace_push_return_trace() before ftrace_graph_entry() and therefore has
> > the small advantage that trace.depth gets initialized automatically.
>
> Well, this is not true. AFAICS arm, x86 and powerpc have same order, and
> other archs have different (inverted) order. And it'd really great if
> all archs agreed on a single ordering.
Ooops. Anyway.. I just realized that we also have an out-of-tree patch
that relies on the now new order on s390. So that patch got a bit smaller
as an added bonus ;)
next prev parent reply other threads:[~2013-10-11 8:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 5:05 [RFC/PATCH] ftrace: add set_graph_notrace filter Namhyung Kim
2013-09-30 7:04 ` Namhyung Kim
2013-10-01 3:58 ` Steven Rostedt
2013-10-10 1:51 ` Namhyung Kim
2013-10-10 2:11 ` Steven Rostedt
2013-10-11 4:17 ` Steven Rostedt
2013-10-11 7:21 ` Heiko Carstens
2013-10-11 8:34 ` Namhyung Kim
2013-10-11 8:58 ` Heiko Carstens [this message]
2013-10-11 12:22 ` Steven Rostedt
2013-10-11 8:19 ` Namhyung Kim
2013-10-11 12:31 ` Steven Rostedt
2013-10-14 0:59 ` Namhyung Kim
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=20131011085809.GD4154@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=schwidefsky@de.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