public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@redhat.com>
To: Lai Jiangshan <laijs@cn.fujitsu.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: Tue, 13 Jan 2009 18:16:17 -0500	[thread overview]
Message-ID: <20090113231617.GD3210@redhat.com> (raw)
In-Reply-To: <495ADF57.8030008@cn.fujitsu.com>

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?

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.

thanks,

-Jason



  reply	other threads:[~2009-01-13 23:18 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 [this message]
2009-01-14  2:49   ` Lai Jiangshan
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=20090113231617.GD3210@redhat.com \
    --to=jbaron@redhat.com \
    --cc=laijs@cn.fujitsu.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