From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [PATCH] remove unimplemented syscalls noise
Date: Wed, 19 Nov 2003 20:20:42 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106927330102939@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106926030617023@msgid-missing>
>>>>> On Wed, 19 Nov 2003 12:15:23 -0800, "Seth, Rohit" <rohit.seth@intel.com> said:
Rohit> Well, in the case of unaligned faults, there is no other way
Rohit> for an application to know that there were unaligned faults.
Rohit> Whereas for unsupported system calls, the kernel will return
Rohit> ENOSYS and thus the application gets the required
Rohit> notification (so that it can take any action it wants). It
Rohit> does not need to depend on dmesg stuff to find that
Rohit> information out.
True in principle, but in practice, you can't always run strace to
find out what's going on, either because the problem starts in early
boot or because the problem is triggered indirectly through daemons
etc.
Rohit> So, it does make sense to remove this printk (even though it
Rohit> is _debug_) in this path.
I really much favor for distro's to make dmesg -n4 the default. There
is no reason to bother average users with KERN_{NOTICE,INFO,DEBUG}
stuff unless they ask for it.
--david
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
2003-11-19 20:20 ` David Mosberger [this message]
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-106927330102939@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--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