public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Elmer Joandi <elmer@ylenurme.ee>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>, linux-kernel@vger.kernel.org
Subject: Re: Universal debug macros.
Date: Mon, 27 Nov 2000 01:45:33 +0100 (MET)	[thread overview]
Message-ID: <200011270045.BAA13121@cave.bitwizard.nl> (raw)
In-Reply-To: <Pine.LNX.4.10.10011270109020.11180-100000@yle-server.ylenurme.sise> from Elmer Joandi at "Nov 27, 2000 01:30:06 am"

Elmer Joandi wrote:
> 
> 
> On Sun, 26 Nov 2000, Rogier Wolff wrote:
> > Sure it will slow the driver down a bit, because of all those bit-test
> > instructions in the driver. If it bothers you, you get to turn it
> > off. If you are capable of that, you are also capable enough to turn
> > it back on when neccesary.
> 
> Now if there would be simple _unified_ system for switching debug code
> on/off, it would be a real win. That  recompilation-capable enduser would
> not need much knowledge to go "General Setup" or newly created
> "Optimization" section and switch debugging off/on for _all_ network
> drivers or ide drivers for example.

Now, how is say "Red Hat" (*) going to ship kernels? Of course they are
going to turn off debugging. Then I'll be stuck with a non-recompiling
user-in-trouble with a non-debugging-enabled kernel. 

Clients whom I have to tell "please read the kernel-howto" and
recompile your kernel. It's not that hard will not feel "good" about
this. It may seem easy to you, but from some people it is not.


				Roger.

(*) Even if I manage to convince Red Hat not to do this, some
distribution is going to claim that they distribute the "performance"
kernel, and disable debugging in the field. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots. 
* There are also old, bald pilots. 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-27  1:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-26 17:53 [PATCH] removal of "static foo = 0" Elmer Joandi
2000-11-26 18:36 ` Alexander Viro
2000-11-26 19:11   ` Elmer Joandi
2000-11-26 22:49 ` Rogier Wolff
2000-11-26 23:30   ` Universal debug macros Elmer Joandi
2000-11-27  0:45     ` Rogier Wolff [this message]
2000-11-27  1:11       ` Elmer Joandi
2000-11-27  4:25         ` H. Peter Anvin
2000-11-27  5:19           ` Michael Meissner
2000-11-27 16:56           ` Chmouel Boudjnah
2000-11-27 17:47             ` H. Peter Anvin
2000-11-27 17:56               ` Chmouel Boudjnah
2000-11-27 17:58                 ` H. Peter Anvin
2000-11-27 18:10                   ` Chmouel Boudjnah
2000-11-27 18:28                     ` H. Peter Anvin
2000-11-27 18:39                       ` Chmouel Boudjnah
2000-11-27 18:41                         ` H. Peter Anvin
2000-11-27 21:09                   ` Gerhard Mack
2000-11-27  8:35         ` Rogier Wolff
2000-11-27 14:42           ` Elmer Joandi
2000-11-27 14:59             ` Rogier Wolff
2000-11-27 15:58               ` Elmer Joandi
2000-11-28  1:34                 ` Peter Samuelson
2000-11-27 16:37     ` Andrew E. Mileski
2000-11-27 17:01       ` Richard B. Johnson
2000-11-27 17:19         ` Andrew E. Mileski
2000-11-27 18:01           ` Richard B. Johnson
2000-11-27 19:55             ` Andrew E. Mileski

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=200011270045.BAA13121@cave.bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=elmer@ylenurme.ee \
    --cc=linux-kernel@vger.kernel.org \
    /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