linux-btrace.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: linux-btrace@vger.kernel.org
Subject: [PATCH RFC] Adding pit_plot.py
Date: Tue, 11 Nov 2008 22:14:31 +0000	[thread overview]
Message-ID: <491A03C7.7050905@hp.com> (raw)

I'd appreciate it if has any comments on something I've been playing
with _before_ is push it out in the tree. Basically, it's another way to
visualize Q, D & C traces utilizing the xmgrace program. The work-flow
is something like:

% blktrace...
% blkparse -d bp.bin ...
% btt -i bp.bin -P pit ...
% pit_plot.py XXXXpit.dat
% xmgrace XXXXpit.agr

A quickly thrown together document can be found at:

http://free.linux.hp.com/~adb/2008-11-11/pit_plot.pdf

The (crudely crafted) Python script is at:

http://free.linux.hp.com/~adb/2008-11-11/pit_plot.py

And the proposed patch would be at:

http://free.linux.hp.com/~adb/2008-11-11/0001-Added-pit_plot.py.patch

with the synopsis being:

From d05c0f3c9349cd3db31946fa049609c12333dee2 Mon Sep 17 00:00:00 2001
From: Alan D. Brunelle <alan.brunelle@hp.com>
Date: Tue, 11 Nov 2008 17:03:37 -0500
Subject: [PATCH] Added pit_plot.py

Creates an xmgrace plot file from data generated by btt's -P option.

Refer to the documentation for more details.

Signed-off-by: Alan D. Brunelle <alan.brunelle@hp.com>
---
 Makefile                    |    2 +-
 btt/doc/Makefile            |   21 +-
 btt/doc/buttons.eps         |  392 ++
 btt/doc/magnifier-final.eps | 6057 +++++++++++++++++++++++++++++++
 btt/doc/magnifier-post.eps  | 6224 +++++++++++++++++++++++++++++++
 btt/doc/magnifier-pre.eps   | 8468
+++++++++++++++++++++++++++++++++++++++++++
 btt/doc/ori-screen.eps      | 8368
++++++++++++++++++++++++++++++++++++++++++
 btt/doc/pit_plot.tex        |  205 ++
 btt/pit_plot.py             |  475 +++
 9 files changed, 30206 insertions(+), 6 deletions(-)


                 reply	other threads:[~2008-11-11 22:14 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=491A03C7.7050905@hp.com \
    --to=alan.brunelle@hp.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).