All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/2] ocfs2: add trace event support for ocfs2
Date: Tue, 13 Oct 2009 13:33:46 -0700	[thread overview]
Message-ID: <20091013203346.GC23257@mail.oracle.com> (raw)
In-Reply-To: <200909170419.n8H4JFWY027973@rgminet13.oracle.com>

On Thu, Sep 17, 2009 at 06:19:44AM +0800, Wengang Wang wrote:
> following patches add trace event support for ocfs2.

Wengang,
	This looks like a nice start.  Thank you for getting this going.
I'm sorry I haven't gotten back until now, I've been busy.
	What I'd like to do next is get a small starting set of
tracepoints.  You have one tracepoint in this patch as a good example,
but we should get a few more.  I don't want every mlog changed into a
tracepoint.  Some of them are old and useless :-)  Instead, I'd like to
find information we often want while debugging.
	Tao, Tiger, and Sunil, what are parts of the code you often come
across when debugging?  Certain mlog() prints you always find really
important to see.  If you point them out, Wengang can cook up
tracepoints for them.

Joel

-- 

"But all my words come back to me
 In shades of mediocrity.
 Like emptiness in harmony
 I need someone to comfort me."

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127

  parent reply	other threads:[~2009-10-13 20:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 22:19 [Ocfs2-devel] [PATCH 0/2] ocfs2: add trace event support for ocfs2 Wengang Wang
2009-09-17  7:51 ` Wengang Wang
2009-10-13 20:33 ` Joel Becker [this message]
2009-10-14  1:07   ` Wengang Wang
2009-10-15  3:05   ` Tao Ma
2009-10-15  9:15     ` Joel Becker
2009-10-15 22:29       ` TaoMa

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=20091013203346.GC23257@mail.oracle.com \
    --to=joel.becker@oracle.com \
    --cc=ocfs2-devel@oss.oracle.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 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.