From: Randy Dunlap <randy.dunlap@oracle.com>
To: prasad@linux.vnet.ibm.com
Cc: David Wilder <dwilder@us.ibm.com>,
linux-kernel@vger.kernel.org, mathieu.desnoyers@polymtl.ca,
hunt@redhat.com, michaele@au1.ibm.com, dave@linux.vnet.ibm.com
Subject: Re: [RFC Patch 1/1] debugfs_printk and debugfs_dump interface
Date: Tue, 22 Apr 2008 07:53:33 -0700 [thread overview]
Message-ID: <480DFBED.8020304@oracle.com> (raw)
In-Reply-To: <20080422052222.GA6623@in.ibm.com>
K. Prasad wrote:
> This patch introduces two new interfaces called debugfs_printk and
> debugfs_dump which can be used to print to the debugfs mount directly.
> It uses the 'trace' infrastructure underneath and is a patch over it.
> A sample file is also created to demonstrate its ease of use.
>
> Signed-off-by: K.Prasad <prasad@linux.vnet.ibm.com>
> ---
> Documentation/trace.txt | 21 ++++
> include/linux/trace.h | 55 +++++++++++
> lib/trace.c | 193 +++++++++++++++++++++++++++++++++++++++--
> samples/trace/Makefile | 2
> samples/trace/fork_new_trace.c | 97 ++++++++++++++++++++
> 5 files changed, 362 insertions(+), 6 deletions(-)
> +
> +/**
> + * debugfs_printk - Output binary into debugfs mount 'directly' using 'trace'
Oops. This is the debugfs_dump() function.
Otherwise it looks good. Thanks.
> + * @dpk: Structure containing info such as parent_dir and directory
> + * @output: Data that needs to be output
> + * @output_len: Length of the output data
> + */
> +int debugfs_dump(struct debugfs_printk_data *dpk, const void *output,
> + const int output_len)
> +{
--
~Randy
next prev parent reply other threads:[~2008-04-22 15:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 11:14 [RFC Patch 0/1] Enhancements to 'trace' infrastructure K. Prasad
2008-04-15 11:26 ` [RFC Patch 1/1] debugfs_printk and debugfs_dump interface K. Prasad
2008-04-16 21:25 ` David Wilder
2008-04-21 12:43 ` K. Prasad
2008-04-21 17:14 ` Randy Dunlap
2008-04-22 5:22 ` K. Prasad
2008-04-22 14:53 ` Randy Dunlap [this message]
2008-04-23 7:59 ` K. Prasad
2008-04-24 21:23 ` David Wilder
2008-04-25 7:42 ` K. Prasad
2008-04-25 8:19 ` K. Prasad
2008-04-28 0:50 ` Michael Ellerman
2008-04-28 4:48 ` K. Prasad
2008-04-28 4:54 ` Michael Ellerman
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=480DFBED.8020304@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=dave@linux.vnet.ibm.com \
--cc=dwilder@us.ibm.com \
--cc=hunt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=michaele@au1.ibm.com \
--cc=prasad@linux.vnet.ibm.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