From: Michael Ellerman <michael@ellerman•id.au>
To: Pekka Enberg <penberg@cs•helsinki.fi>
Cc: linux-kernel@vger•kernel.org, openib-general@openib•org,
linuxppc-dev@ozlabs•org, "Christoph Raisch" <RAISCH@de•ibm.com>,
"Hoang-Nam Nguyen" <HNGUYEN@de•ibm.com>,
"Marcus Eder" <MEDER@de•ibm.com>,
"Jörn Engel" <joern@wohnheim•fh-wedel.de>
Subject: Re: [openib-general] Re: [PATCH 04/16] ehca: userspace support
Date: Fri, 28 Apr 2006 17:11:32 +1000 [thread overview]
Message-ID: <1146208292.6307.4.camel@localhost.localdomain> (raw)
In-Reply-To: <84144f020604272332s6101032cy6936096230f3637c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
On Fri, 2006-04-28 at 09:32 +0300, Pekka Enberg wrote:
> Hi Heiko,
>
> On 4/28/06, Heiko J Schick <info@schihei•de> wrote:
> > 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.
Yeah, I really don't think you want to be running with that kind of
debugging gunk in a production kernel. Is someone who can't build their
own kernel really going to be able to make sense of the output?
cheers
--
Michael Ellerman
IBM OzLabs
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-04-28 7:11 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 [this message]
2006-04-29 6:38 ` Heiko J Schick
2006-04-29 7:08 ` Heiko Carstens
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=1146208292.6307.4.camel@localhost.localdomain \
--to=michael@ellerman$(echo .)id.au \
--cc=HNGUYEN@de$(echo .)ibm.com \
--cc=MEDER@de$(echo .)ibm.com \
--cc=RAISCH@de$(echo .)ibm.com \
--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