|| ||Greg Banks <gnb-sJ/iWh9BUns@public.gmane.org>|
|| ||Linux Kernel ML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>|
|| ||[patch 0/5] activate & deactivate dprintks individually and severally|
|| ||Tue, 20 Jan 2009 12:29:30 +1100|
|| ||Linux NFS ML <linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux NFSv4 ML <nfsv4-6DNke4IJHB0gsBAKwltoeQ@public.gmane.org>,
SystemTAP ML <systemtap-R2MHTz/CkKAf7BdofF/totBPR1lH4CV8@public.gmane.org>|
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.
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html