From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] remove unimplemented syscalls noise
Date: Wed, 19 Nov 2003 20:20:20 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106927324202872@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106926030617023@msgid-missing>
On Wed, Nov 19, 2003 at 12:11:03PM -0800, David Mosberger wrote:
> >>>>> On Wed, 19 Nov 2003 19:54:02 +0000, Matthew Wilcox <willy@debian.org> said:
>
> Matthew> This is the same thing as printing the user unaligned
> Matthew> exceptions. It's something no other architecture does, and
> Matthew> for a reason, which has been explained to you before, but
> Matthew> you don't want to fix it.
>
> And yet both features are incredibly useful when debugging, something
> you seem to ignore.
No, it *isn't*. The majority of systems in use are not being debugged
(regardless of how you & I spend most of our time). Having these
messages constantly stream past in dmesg (which no other architecture
does) serves only to potentially mask other, useful pieces of information
and confuse the customer.
Every time we emit something to the system log, it's a potential support
call. Our friends in other parts of HP are already unhappy with how much
output Linux produces even when everything's OK. It's also a sysadmin
hassle as logfiles fill up more quickly when this kind of junk goes by.
I'm sure this was useful for debugging once, but those days are gone.
We need to print less of this stuff. Something a lot of places do is:
#undef DEBUG
#ifdef DEBUG
#define DBG(x...) printk(x)
#else
#define DBG(x...)
#endif
Would it mollify you if these printks were turned into DBGs?
Or perhaps better, we could use pr_debug() from <linux/kernel.h>.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-11-19 20:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 16:42 [PATCH] remove unimplemented syscalls noise Kyle McMartin
2003-11-19 19:44 ` David Mosberger
2003-11-19 19:54 ` Matthew Wilcox
2003-11-19 20:11 ` David Mosberger
2003-11-19 20:15 ` Seth, Rohit
2003-11-19 20:20 ` Matthew Wilcox [this message]
2003-11-19 20:20 ` David Mosberger
2003-11-19 20:33 ` David Mosberger
2003-11-19 20:35 ` Matthew Wilcox
2003-11-19 21:13 ` Rich Altmaier
2003-11-19 21:21 ` David Mosberger
2003-11-19 21:31 ` David Mosberger
2003-11-19 23:13 ` Matthias Fouquet-Lapar
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=marc-linux-ia64-106927324202872@msgid-missing \
--to=willy@debian.org \
--cc=linux-ia64@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