public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Seth, Rohit" <rohit.seth@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [PATCH] remove unimplemented syscalls noise
Date: Wed, 19 Nov 2003 20:15:23 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106927294002395@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106926030617023@msgid-missing>

Well, in the case of unaligned faults, there is no other way for an
application to know that there were unaligned faults.  Whereas for
unsupported system calls, the kernel will return ENOSYS and thus the
application gets the required notification (so that it can take any
action it wants).  It does not need to depend on dmesg stuff to find
that information out.  

So, it does make sense to remove this printk (even though it is _debug_)
in this path.

> -----Original Message-----
> From: linux-ia64-owner@vger.kernel.org [mailto:linux-ia64-
> owner@vger.kernel.org] On Behalf Of Matthew Wilcox
> Sent: Wednesday, November 19, 2003 11:54 AM
> To: davidm@hpl.hp.com
> Cc: Kyle McMartin; linux-ia64@vger.kernel.org
> Subject: Re: [PATCH] remove unimplemented syscalls noise
> 
> On Wed, Nov 19, 2003 at 11:44:46AM -0800, David Mosberger wrote:
> > What's wrong with dmesg -n4?  Those messages are marked KERN_DEBUG
for
> > a reason.  BTW: Red Hat does this by default, but Debian doesn't.
In
> > my opinion, Red Hat does the right thing here: by default, most
user's
> > don't care about such messages, but they're invaluable when tracking
> > down problems.
> 
> This is the same thing as printing the user unaligned exceptions.
> It's something no other architecture does, and for a reason, which has
> been explained to you before, but you don't want to fix it.  *sigh*.
> 
> --
> "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
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64"
in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2003-11-19 20:15 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 [this message]
2003-11-19 20:20 ` Matthew Wilcox
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-106927294002395@msgid-missing \
    --to=rohit.seth@intel.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