All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alan D. Brunelle" <Alan.Brunelle@pobox.com>
To: linux-btrace@vger.kernel.org
Subject: [PATCH btrace] Add in -r support for btrace
Date: Fri, 11 May 2007 13:21:35 +0000	[thread overview]
Message-ID: <46446DDF.7050108@pobox.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 265 bytes --]

Using Ubuntu, debugfs is mounted on /debug instead of /sys/kernel/debug. 
[Perhaps, we should put in blktrace a search through "common" areas 
where debug could be mounted, and or do a simple parsing of the output 
from a 'mount' command to /find/ the directory.]


[-- Attachment #2: btrace --]
[-- Type: text/plain, Size: 947 bytes --]

#!/bin/sh
# Copyright (c) 2005 Silicon Graphics, Inc.
# All rights reserved.
# 
#	Nathan Scott <nathans@sgi.com>
#	14 Sep 2005	Initial version
# 

TRACEOPTS=""
PARSEOPTS="-b100000"
SUMMARIZE=""
USAGE="Usage: btrace [-s] [-t] [-S] [-w N] [-a <trace>...] [-r <dbg mnt]<dev>..."
DIRNAME=`dirname $0`

while getopts "a:r:stSw:hv" c
do
	case $c in
	a)	TRACEOPTS=$TRACEOPTS" -a "$OPTARG" ";;
	w)	TRACEOPTS=$TRACEOPTS" -w "$OPTARG" ";;
	n)	TRACEOPTS=$TRACEOPTS" -n "$OPTARG" ";;
	b)	TRACEOPTS=$TRACEOPTS" -b "$OPTARG" ";;
	r)	TRACEOPTS=$TRACEOPTS" -r "$OPTARG" ";;
	s)	PARSEOPTS=$PARSEOPTS" -s";;
	t)	PARSEOPTS=$PARSEOPTS" -t";;
	h)	PARSEOPTS=$PARSEOPTS" -h";;
	v)	PARSEOPTS=$PARSEOPTS" -v";;
	S)	SUMMARIZE="";;
	\?)	echo $USAGE 1>&2
		exit 2
		;;
	esac
done
PARSEOPTS="${PARSEOPTS} ${SUMMARIZE}"

shift `expr $OPTIND - 1`
if [ $# -eq 0 ]; then
	echo $USAGE 1>&2
	exit 2
fi

${DIRNAME}/blktrace ${TRACEOPTS} -o- $@ | ${DIRNAME}/blkparse ${PARSEOPTS} -i-

             reply	other threads:[~2007-05-11 13:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-11 13:21 Alan D. Brunelle [this message]
2007-05-11 13:43 ` [PATCH btrace] Add in -r support for btrace Jens Axboe

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=46446DDF.7050108@pobox.com \
    --to=alan.brunelle@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.