All of lore.kernel.org
 help / color / mirror / Atom feed
From: "zhangwei(Jovi)" <jovi.zhangwei@huawei.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] tracing: add ftrace_trace_stack into __trace_puts/__trace_bputs
Date: Mon, 5 Aug 2013 11:07:22 +0800	[thread overview]
Message-ID: <51FF16EA.7000501@huawei.com> (raw)
In-Reply-To: <51E7A7C9.9040401@huawei.com>

On 2013/7/18 16:31, zhangwei(Jovi) wrote:
> Currently trace option stacktrace is not applicable for
> trace_printk with constant string argument, the reason is
> there missed ftrace_trace_stack in __trace_puts/__trace_bputs.
> 
> In contrast, when using trace_printk with not constant string
> argument(will call into __trace_printk/__trace_bprintk), then
> trace option stacktrace is workable, this inconstant result
> will confusing user a lot.
> 

Hi steven,

How about this patch?
and [PATCH 2/3] "tracing: add TRACE_ITER_PRINTK flag check in __trace_puts/__trace_bputs"

Thanks.

jovi.

> Signed-off-by: zhangwei(Jovi) <jovi.zhangwei@huawei.com>
> ---
>  kernel/trace/trace.c |   12 ++++++++++--
>  1 file changed, 10 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index 3d5a931..4d70cc5 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -363,13 +363,16 @@ int __trace_puts(unsigned long ip, const char *str, int size)
>  	struct print_entry *entry;
>  	unsigned long irq_flags;
>  	int alloc;
> +	int pc;
> +
> +	pc = preempt_count();
> 
>  	alloc = sizeof(*entry) + size + 2; /* possible \n added */
> 
>  	local_save_flags(irq_flags);
>  	buffer = global_trace.trace_buffer.buffer;
>  	event = trace_buffer_lock_reserve(buffer, TRACE_PRINT, alloc,
> -					  irq_flags, preempt_count());
> +					  irq_flags, pc);
>  	if (!event)
>  		return 0;
> 
> @@ -386,6 +389,7 @@ int __trace_puts(unsigned long ip, const char *str, int size)
>  		entry->buf[size] = '\0';
> 
>  	__buffer_unlock_commit(buffer, event);
> +	ftrace_trace_stack(buffer, irq_flags, 4, pc);
> 
>  	return size;
>  }
> @@ -403,11 +407,14 @@ int __trace_bputs(unsigned long ip, const char *str)
>  	struct bputs_entry *entry;
>  	unsigned long irq_flags;
>  	int size = sizeof(struct bputs_entry);
> +	int pc;
> +
> +	pc = preempt_count();
> 
>  	local_save_flags(irq_flags);
>  	buffer = global_trace.trace_buffer.buffer;
>  	event = trace_buffer_lock_reserve(buffer, TRACE_BPUTS, size,
> -					  irq_flags, preempt_count());
> +					  irq_flags, pc);
>  	if (!event)
>  		return 0;
> 
> @@ -416,6 +423,7 @@ int __trace_bputs(unsigned long ip, const char *str)
>  	entry->str			= str;
> 
>  	__buffer_unlock_commit(buffer, event);
> +	ftrace_trace_stack(buffer, irq_flags, 4, pc);
> 
>  	return 1;
>  }
> 



  reply	other threads:[~2013-08-05  3:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18  8:31 [PATCH 1/3] tracing: add ftrace_trace_stack into __trace_puts/__trace_bputs zhangwei(Jovi)
2013-08-05  3:07 ` zhangwei(Jovi) [this message]
2014-07-09 18:40 ` Steven Rostedt

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=51FF16EA.7000501@huawei.com \
    --to=jovi.zhangwei@huawei.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.