From: linas@austin.ibm.com (Linas Vepstas)
To: Milton Miller <miltonm@bga.com>
Cc: Olof Johansson <olof@lixom.net>, ppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] hvc_console polling mode timer backoff
Date: Mon, 16 Apr 2007 12:03:28 -0500 [thread overview]
Message-ID: <20070416170328.GD8281@austin.ibm.com> (raw)
In-Reply-To: <97762565fcdccbf85d1d04cd055b1197@bga.com>
On Sat, Apr 14, 2007 at 02:42:02PM -0500, Milton Miller wrote:
>
> Did you consider making MAX_TIMEOUT a module parameter? It could then
> be changed at runtime through /sys/modules/.
There's a philosophy (that I have warmed up to over time) that
says that too much kernel configurability is a bad thing.
Less configurability makes problems easier to debug: you don't
have to worry about:
-- bugs that occur for only certain parameter settings
-- some dang-fool user/sysadmin setting the timout to
1000 seconds (mistaking seconds for milliseconds) and
then reporting a bug.
-- the latest fedora core having some udev script that
finds the hvc console and slaps some crazy values into it.
Surely, we have all known that bright-eyed, bushy-tailed
developer who, when they ask you for help with a bug,
your first questions are "did you mess with it?" and
"which part did you mess with?"
--linas
next prev parent reply other threads:[~2007-04-16 17:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 16:14 [PATCH] hvc_console polling mode timer backoff Will Schmidt
2007-04-12 16:17 ` [PATCH] hvc_console typo corrections Will Schmidt
2007-04-12 17:33 ` [PATCH] hvc_console polling mode timer backoff Linas Vepstas
2007-04-12 18:43 ` Will Schmidt
2007-04-12 19:09 ` Olof Johansson
2007-04-13 0:45 ` Michael Ellerman
2007-04-13 1:56 ` Olof Johansson
2007-04-13 7:47 ` Michael Ellerman
2007-04-13 16:46 ` Linas Vepstas
2007-04-13 19:11 ` Will Schmidt
2007-04-15 13:33 ` Michael Ellerman
2007-04-16 19:34 ` Will Schmidt
2007-04-14 19:42 ` Milton Miller
2007-04-16 17:03 ` Linas Vepstas [this message]
2007-04-16 20:22 ` Will Schmidt
2007-04-16 21:59 ` Linas Vepstas
2007-04-17 0:13 ` Michael Ellerman
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=20070416170328.GD8281@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.com \
--cc=olof@lixom.net \
/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;
as well as URLs for NNTP newsgroup(s).