From: Greg Banks <gnb@sgi.com>
To: Linux Kernel ML <linux-kernel@vger.kernel.org>
Cc: Linux NFS ML <linux-nfs@vger.kernel.org>,
Linux NFSv4 ML <nfsv4@linux-nfs.org>,
SystemTAP ML <systemtap@sources.redhat.com>
Subject: [patch 0/5] activate & deactivate dprintks individually and severally
Date: Tue, 20 Jan 2009 01:33:00 -0000 [thread overview]
Message-ID: <20090120012930.020621000@sgi.com> (raw)
As mentioned in the recent discussion on NFS trace points on the NFS &
SystemTap mailing lists. This patch allows field support staff and
kernel developers debug kernel problems, by enabling them to treat
dprintks as precise trace points rather than syslog spamming tools.
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. 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.
Jason Baron suggested I post it here for review and contrast with
his dynamic dprintk feature.
--
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-20 1:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 1:33 Greg Banks [this message]
2009-01-20 1:33 ` [patch 1/5] Move definitions of struct module_sect_attr back into module.h Greg Banks
2009-01-20 1:33 ` [patch 5/5] Add a module to test the dprintk module Greg Banks
2009-01-20 1:33 ` [patch 3/5] Make the dprintk() macro record information about the callsite Greg Banks
2009-01-20 1:41 ` [patch 4/5] Add the dprintk module to allow dprintks to be activated/deactivated singly Greg Banks
2009-01-20 16:25 ` [patch 2/5] Add apply_modules() which applies a function to each module Greg Banks
2009-01-21 16:42 ` [patch 0/5] activate & deactivate dprintks individually and severally 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=20090120012930.020621000@sgi.com \
--to=gnb@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--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).