Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: laijs@cn.fujitsu.com (Lai Jiangshan)
Subject: [ltt-dev] [PATCH 00/13] textoutput: implement text output for lttng
Date: Tue, 13 Jan 2009 17:08:28 +0800	[thread overview]
Message-ID: <496C5A0C.20208@cn.fujitsu.com> (raw)


text output helps kernel developer trace the kernel directly.

text output include these:

1) Marker ID management
   Marker ID identify every type of event,
   a) ASCII text output needs get name&fmt from eID faster.
   b) Marker ID and its data must be permanent.

patches:
	01/13: make marker_entry permanent
	02/13: get name and fmt from permanent eID

2) ltt-relay events traveling

patches:
	07/13: implement fmt align
	11/13: implement ltt-ascii (the core patch for text output)

3) event reader
   get significative binary data from event. and convert them to a va_list
   or other type. binary in event is raw data, we must know its meaning for
   formating.

patches:
	03/13: read event header from ltt-relay buffer
	07/13: implement fmt align  (skip pending data)
	04/13: read C-style string from ltt-relay buffer
	05/13: read basic type from  ltt-relay buffer

4) event text formator
   format data to text.

patches:
	06/13: introduce ltt_serialize_printf()
	11/13: implement ltt-ascii

5) create files for text output and control
	11/13: implement ltt-ascii
	12/13: enable text output for ltt-relay
	13/13: enable text output for ltt-relay-locked

6) misc
	08/13: get&put chan&chan_buf's reference
	09/13: enable accessing struct ltt_channel_buf_struct
	10/13: implement text output framework
	11/13: implement ltt-ascii

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







                 reply	other threads:[~2009-01-13  9:08 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=496C5A0C.20208@cn.fujitsu.com \
    --to=laijs@cn.fujitsu.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