From: "Frank Ch. Eigler" <fche@redhat.com>
To: Andre Detsch <adetsch@br.ibm.com>
Cc: systemtap@sources.redhat.com
Subject: Re: [PATCH] Update SCSI tapset
Date: Wed, 23 Dec 2009 20:56:00 -0000 [thread overview]
Message-ID: <20091223205619.GA2785@redhat.com> (raw)
In-Reply-To: <4B32681C.7010300@br.ibm.com>
Hi -
On Wed, Dec 23, 2009 at 04:57:32PM -0200, Andre Detsch wrote:
> [...] Currently, the only usage example is
> "testsuite/buildok/scsi.stp". It covers all tapsets/scsi.stp
> probes. If it is good to have something inside
> testsuite/systemtap.examples/io/, maybe moving or copying content
> from testsuite/buildok/scsi.stp [...]
We have heard interest in probe scripts that focus in on *errors*,
specifically to display recent history of I/O up to the point of a
low-level error associated with the device. Do you think you could
write something like that?
- FChE
next prev parent reply other threads:[~2009-12-23 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 22:13 Andre Detsch
2009-12-18 17:19 ` Frank Ch. Eigler
2009-12-23 18:57 ` Andre Detsch
2009-12-23 20:56 ` Frank Ch. Eigler [this message]
2009-12-22 18:13 ` K.Prasad
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=20091223205619.GA2785@redhat.com \
--to=fche@redhat.com \
--cc=adetsch@br.ibm.com \
--cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).