From: Steven Rostedt <rostedt@goodmis.org>
To: Nikolay Borisov <nborisov@suse.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] ftrace: Fix depth filtering when func_stack is enabled.
Date: Mon, 22 Jan 2018 18:16:49 -0500 [thread overview]
Message-ID: <20180122181649.7486d421@gandalf.local.home> (raw)
In-Reply-To: <1516629004-16658-1-git-send-email-nborisov@suse.com>
On Mon, 22 Jan 2018 15:50:04 +0200
Nikolay Borisov <nborisov@suse.com> wrote:
> diff --git a/kernel/trace/trace_functions.c b/kernel/trace/trace_functions.c
> index 27f7ad12c4b1..b721f1f3f3c0 100644
> --- a/kernel/trace/trace_functions.c
> +++ b/kernel/trace/trace_functions.c
> @@ -181,14 +181,11 @@ function_stack_trace_call(unsigned long ip, unsigned long parent_ip,
> pc = preempt_count();
> trace_function(tr, ip, parent_ip, flags, pc);
> /*
> - * skip over 5 funcs:
> - * __ftrace_trace_stack,
> - * __trace_stack,
> + * skip over 2 funcs:
> * function_stack_trace_call
> - * ftrace_list_func
Thanks, but this breaks when you are not using ORC unwinder.
> * ftrace_call
> */
> - __trace_stack(tr, flags, 5, pc);
> + __trace_stack(tr, flags, 2, pc);
> }
>
> atomic_dec(&data->disabled);
There's a bit of ORC unwinder breakage that I'm still dealing with. I
also have patches to handle the differences between ORC and FP, in the
__trace_stack() usages. I'm hoping to have this all fixed by tomorrow,
as I'll be traveling after that.
Thanks!
-- Steve
next prev parent reply other threads:[~2018-01-22 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 13:50 Nikolay Borisov
2018-01-22 23:16 ` Steven Rostedt [this message]
2018-01-23 6:58 ` Nikolay Borisov
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=20180122181649.7486d421@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nborisov@suse.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
all inboxes | Powered by JetHome®