From: Heiko Carstens <heiko.carstens@de•ibm.com>
To: Heiko J Schick <info@schihei•de>
Cc: linux-kernel@vger•kernel.org, openib-general@openib•org,
linuxppc-dev@ozlabs•org, Pekka Enberg <penberg@cs•helsinki.fi>,
Hoang-Nam Nguyen <HNGUYEN@de•ibm.com>,
Marcus Eder <MEDER@de•ibm.com>,
Christoph Raisch <RAISCH@de•ibm.com>,
J?rn Engel <joern@wohnheim•fh-wedel.de>
Subject: Re: [openib-general] Re: [PATCH 04/16] ehca: userspace support
Date: Sat, 29 Apr 2006 09:08:26 +0200 [thread overview]
Message-ID: <20060429070826.GA9463@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <4044CACC-FB5A-415E-8974-27136269B5C1@schihei.de>
> >>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.
prev parent reply other threads:[~2006-04-29 10:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 10:48 [PATCH 04/16] ehca: userspace support Heiko J Schick
2006-04-27 11:43 ` Jörn Engel
2006-04-27 22:36 ` Michael Ellerman
2006-04-28 6:11 ` [openib-general] " Heiko J Schick
2006-04-28 6:32 ` Pekka Enberg
2006-04-28 7:11 ` Michael Ellerman
2006-04-29 6:38 ` Heiko J Schick
2006-04-29 7:08 ` Heiko Carstens [this message]
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=20060429070826.GA9463@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de$(echo .)ibm.com \
--cc=HNGUYEN@de$(echo .)ibm.com \
--cc=MEDER@de$(echo .)ibm.com \
--cc=RAISCH@de$(echo .)ibm.com \
--cc=info@schihei$(echo .)de \
--cc=joern@wohnheim$(echo .)fh-wedel.de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=openib-general@openib$(echo .)org \
--cc=penberg@cs$(echo .)helsinki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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