mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "K.Prasad" <prasad@linux.vnet.ibm.com>
To: "kernel list" <linux-kernel@vger.kernel.org>
Cc: dwilder@us.ibm.com, akpm@linux-foundation.org,
	"prasad@linux.vnet.ibm.com" <prasad@linux.vnet.ibm.com>
Subject: [Patch 0/1] Enhancements to 'trace' infrastructure - v2
Date: Fri, 16 May 2008 22:31:51 +0530	[thread overview]
Message-ID: <op.ua9axd2a03j166@prasadkr_t60p.in.ibm.com> (raw)

Hi All,
	Please review the following patch which introduces two new
interfaces to output data using 'trace' infrastructure. These interfaces
can be used to print directly onto a debugfs mount. Since it uses
'trace'
interface underneath the directory and file structures are as created by
'trace'.

The proposed trace_* interfaces are meant to overcome the need to
setup/tear-down 'trace' infrastructure by the user. In addition to this
the patches help in:

a) Printing out data into a debugfs mounted file without bothering about
creating/re-using debugfs files, sizes of intermediate buffers, etc.
(This is achieved through the functions init_trace_interface() and
trace_exists()).
b) Provide interfaces to do i)string output or ii)binary dump of data
c) Tear-down of the trace infrastructure through a single function call
using its parent directory name, and unmindful of the internal data
structures such as 'struct trace_info'.(using trace_cleanup_all)
d) The trace_printk_data may be further enhanced to provide features
suh as the ability to invoke pre- and post- printing callback functions
For e.g. A callback function to obtain a given lock before printing out
a given data, etc.

A quick look at samples/trace/fork_trace.c would help understand what is
required to get data out using the 'trace' infrastructure (vs the
proposed interfaces which have been exemplified in
samples/trace/fork_new_trace.c).

The patches are based against 2.6.25-mm1 and have been tested on an
i386 machine.

Thanks,
K.Prasad

             reply	other threads:[~2008-05-16 17:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 17:01 K.Prasad [this message]
2008-05-16 17:04 ` [RFC Patch 1/1] trace_printk and trace_dump interface " K.Prasad
2008-05-17  2:22   ` K.Prasad
2008-05-19 23:21     ` Andrew Morton
2008-05-20 19:53       ` K.Prasad
2008-05-20 20:12         ` Andrew Morton
2008-05-23  4:37           ` K.Prasad
2008-05-28 18:16             ` K.Prasad
2008-05-28 18:37               ` [RFC Patch 0/1] Merging Documentation/trace.txt with Documentation/filesystems/relay.txt K.Prasad
2008-05-28 18:48               ` [RFC Patch 2/2] Renaming lib/trace.[ch] files to kernel/relay_debugfs.[ch] and enhancements K.Prasad
2008-05-19 20:02   ` [RFC Patch 1/1] trace_printk and trace_dump interface - v2 David Wilder

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=op.ua9axd2a03j166@prasadkr_t60p.in.ibm.com \
    --to=prasad@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=dwilder@us.ibm.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®