From: Greg Banks <gnb@sgi.com>
To: Linux NFS ML <linux-nfs@vger.kernel.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>
Subject: [patch 0/5] activate & deactivate dprintks individually and severally
Date: Mon, 19 Jan 2009 17:40:18 +1100 [thread overview]
Message-ID: <20090119064018.442220000@sgi.com> (raw)
As mentioned in the recent discussion on NFS trace points.
This is a forward ported (from 2.6.16), updated, and split version
of a patch that has been used in SGI's internal development tree for
the last few months. It's designed to help field support staff and
kernel developers debug kernel problems, by enabling them to treat
dprintks as precise trace points rather than syslog spamming tools.
The very first version of this was used about eighteen months ago
when debugging NFS/RDMA, which has an enormous number of dprintks
and no other way to debug it.
--
Greg Banks, P.Engineer, SGI Australian Software Group.
the brightly coloured sporks of revolution.
I don't speak for SGI.
next reply other threads:[~2009-01-19 6:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 6:40 Greg Banks [this message]
2009-01-19 6:40 ` [patch 1/5] Move definitions of struct module_sect_attr back into module.h Greg Banks
2009-01-19 6:40 ` [patch 2/5] Add apply_modules() which applies a function to each module Greg Banks
2009-01-19 6:40 ` [patch 3/5] Make the dprintk() macro record information about the callsite Greg Banks
2009-01-19 6:40 ` [patch 4/5] Add the dprintk module to allow dprintks to be activated/deactivated singly Greg Banks
2009-01-19 6:40 ` [patch 5/5] Add a (not built) module to test the dprintk module Greg Banks
-- strict thread matches above, loose matches on Subject: below --
2009-01-20 1:29 [patch 0/5] activate & deactivate dprintks individually and severally Greg Banks
2009-01-21 15:28 ` Jason Baron
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=20090119064018.442220000@sgi.com \
--to=gnb@sgi.com \
--cc=fche@redhat.com \
--cc=linux-nfs@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