Messages in this thread | | | Date | Sat, 29 Apr 2006 09:08:26 +0200 | From | Heiko Carstens <> | Subject | Re: [openib-general] Re: [PATCH 04/16] ehca: userspace support |
| |
> >>The problem I see with pr_debug() is that it could only activated via > >>a compile flag. To use the debug outputs you have to re-compile / > >>compile your own kernel. > > > >Do you really need this heavy debug logging in the first place? You > >can use kprobes for arbitrary run-time inspection anyway, so logging > >everything seems wasteful. > > The problem I see with kprobes is that you have to set several kernel > configuration options (e.g. CONFIG_KPROBES, CONFIG_DEBUG_INFO, etc.) > on compile time to use it. Same problem with pr_debug().
It might be worth to move the s390 debug feature to common code. At least it has proven many times to be very useful in device driver debugging... See Documentation/s390/s390dbf.txt and arch/s390/kernel/debug.c. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |