From: Edward Shishkin <edward@redhat.com>
To: linux-btrace@vger.kernel.org
Subject: [patch 2/6] blktrace: blkiomon documentation update
Date: Fri, 30 Jul 2010 14:04:24 +0000 [thread overview]
Message-ID: <4C52DBE8.4020206@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 67 bytes --]
--
Edward O. Shishkin
Principal Software Engineer
Red Hat Czech
[-- Attachment #2: 9-blktrace-fix-595419.patch --]
[-- Type: text/plain, Size: 1409 bytes --]
Fixup for 595419.
Document blkiomon option -d (--dump-lldd).
Add drv_data mask description to blktrace man page.
Signed-off-by: Edward Shishkin <edward@redhat.com>
---
--- blktrace-1.0.1.orig/blkiomon.c
+++ blktrace-1.0.1/blkiomon.c
@@ -599,6 +599,7 @@
"-I <interval> | --interval=<interval>\n" \
"[ -h <file> | --human-readable=<file> ]\n" \
"[ -b <file> | --binary=<file> ]\n" \
+ "[ -d <file> | --dump-lldd=<file> ]\n" \
"[ -D <file> | --debug=<file> ]\n" \
"[ -Q <path name> | --msg-queue=<path name>]\n" \
"[ -q <msg queue id> | --msg-queue-id=<msg queue id>]\n" \
--- blktrace-1.0.1.orig/doc/blkiomon.8
+++ blktrace-1.0.1/doc/blkiomon.8
@@ -7,7 +7,7 @@
.SH SYNOPSIS
.B blkiomon \-I \fIinterval\fR [ \-h \fIfile\fR ] [ \-b \fIfile\fR ]
-[ \-D \fIfile\fR ] [ \-Q \fIpath_name\fR
+[ \-d \fIfile\fR ] [ \-D \fIfile\fR ] [ \-Q \fIpath_name\fR
\-q \fImsg_queue_id\fR \-m \fImsg_id\fR ] [ \-V ]
.br
@@ -50,6 +50,13 @@
Binary output file. Use '\-' for stdout.
.RE
+\-d \fIfile\fR
+.br
+\-\-dump-lldd=\fIfile\fR
+.RS
+Output file for data emitted by low level device driver.
+.RE
+
\-D \fIfile\fR
.br
\-\-debug=\fIfile\fR
--- blktrace-1.0.1.orig/doc/blktrace.8
+++ blktrace-1.0.1/doc/blktrace.8
@@ -172,6 +172,8 @@
\fIwrite\fR: write traces
.br
\fInotify\fR: trace messages
+.br
+\fIdrv_data\fR: additional driver specific trace
.RE
next reply other threads:[~2010-07-30 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 14:04 Edward Shishkin [this message]
2010-07-30 14:38 ` [patch 2/6] blktrace: blkiomon documentation update Alan D. Brunelle
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=4C52DBE8.4020206@redhat.com \
--to=edward@redhat.com \
--cc=linux-btrace@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;
as well as URLs for NNTP newsgroup(s).