public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Jason Baron <jbaron@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/5] ftrace: show ftrace_bprintk()'s formats
Date: Wed, 14 Jan 2009 10:49:56 +0800	[thread overview]
Message-ID: <496D52D4.70202@cn.fujitsu.com> (raw)
In-Reply-To: <20090113231617.GD3210@redhat.com>

Jason Baron wrote:
> On Wed, Dec 31, 2008 at 10:56:23AM +0800, Lai Jiangshan wrote:
>> Impact: let user knows the format
>>
>> Create a file on <debugfs-dir>/tracing/ to show ftrace_bprintk()'s formats.
>>
>> This formats will help for these condition:
>> 1) User get binary data from core file.(formats are backup before coredump)
>> 2) User splice ring_buffer to a file.
>> User can use formats for parsing the binary data in userspace.
>>
> 
> When I 'cat' trace_bprintk_formats on my system the file is empty. This
> seems to be b/c 'ftrace_bprintk' is not being used in this patchset. It
> can't be used in patch #5 during marker register b/c the format wouldn't
> be known at runtime. Thus, as it currently stands this patch, patch 4/5,
> isn't adding much?

If you don't use ftrace_bprintk(), the file trace_bprintk_formats is empty.
This file record all formats which ftrace_bprintk() uses.

You can use ftrace_bprintk() everywhere as another printk().

Patch #5 enables binary printk for markers, this is another additional tool
for tracing markers.

> 
> A thought on how this might be resolved would be to have the core marker
> code pass us its address so this could be recorded in the trace buffer.
> Then, also add some debug file that displays the markers and maps marker
> addresses with format strings.
> 

Patch#5 does it as you said.




  reply	other threads:[~2009-01-14  2:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-31  2:56 [PATCH 4/5] ftrace: show ftrace_bprintk()'s formats Lai Jiangshan
2009-01-13 23:16 ` Jason Baron
2009-01-14  2:49   ` Lai Jiangshan [this message]
2009-01-14 14:25     ` Jason Baron
2009-01-15 10:19       ` Lai Jiangshan

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=496D52D4.70202@cn.fujitsu.com \
    --to=laijs@cn.fujitsu.com \
    --cc=jbaron@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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