From: Steven Rostedt <rostedt@goodmis.org>
To: Nikolay Borisov <nborisov@suse.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: Export trace_dump_stack to modules
Date: Wed, 17 Oct 2018 16:19:23 -0400 [thread overview]
Message-ID: <20181017161923.310ca1a4@gandalf.local.home> (raw)
In-Reply-To: <1539759103-5923-1-git-send-email-nborisov@suse.com>
On Wed, 17 Oct 2018 09:51:43 +0300
Nikolay Borisov <nborisov@suse.com> wrote:
> There is no reason for this function to be unexprted and it's a useful
> debugging aid.
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Thanks, I added this to my queue for the merge window.
-- Steve
> ---
> kernel/trace/trace.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index bf6f1d70484d..15c7a7d01505 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -2727,6 +2727,7 @@ void trace_dump_stack(int skip)
> __ftrace_trace_stack(global_trace.trace_buffer.buffer,
> flags, skip, preempt_count(), NULL);
> }
> +EXPORT_SYMBOL_GPL(trace_dump_stack);
>
> static DEFINE_PER_CPU(int, user_stack_count);
>
prev parent reply other threads:[~2018-10-17 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 6:51 [PATCH] tracing: Export trace_dump_stack to modules Nikolay Borisov
2018-10-17 20:19 ` Steven Rostedt [this message]
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=20181017161923.310ca1a4@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;
as well as URLs for NNTP newsgroup(s).