public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/5] ftrace: support binary record (V2)
Date: Wed, 31 Dec 2008 10:55:49 +0800	[thread overview]
Message-ID: <495ADF35.6090101@cn.fujitsu.com> (raw)

Binary record will save memory in trace buffer, and more events
can be recorded in buffer.

This patch add infrastructure for supporting binary record.

This infrastructure records events by binary and shows events
by human readable text.

And add a API ftrace_bprintk() using this infrastructure.
(This API is exactly the same as ftrace_printk(), beside it
record the date by binary)

changed from V1:
1) not use Python style. Formates typically have 2~8 '%',
   using Python style make no sense, and gcc can not check parameters
   when we use Python style.
2) enable ftrace trace markers.

patches are for tracing/ftrace.

Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
---






                 reply	other threads:[~2008-12-31  2:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=495ADF35.6090101@cn.fujitsu.com \
    --to=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