All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: user-space unaligned accesses
Date: Wed, 08 Oct 2003 22:54:07 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106565367106363@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106562414203331@msgid-missing>

On Wednesday 08 October 2003 3:46 pm, Grant Grundler wrote:
> On Wed, Oct 08, 2003 at 08:42:00AM -0600, Bjorn Helgaas wrote:
> > ...
> > The ia64 architecture does a tty_write
> > on a userspace unaligned access. Not only is this extremenly annoying,
> > it's also very broken since the tty may well be suspended etc etc.
> > Doing a printk on such an access by default is very broken already,
> > lets not make it worse
> 
> This was beat to death on linux-ia64 already where davidm and davem
> decided to disagree on the utility of printing unaligned accesses
> to the tty.

I thought that discussion was mainly about messages printed by the
kernel using printk.  The Red Hat concern was specifically about
writing to the user tty.

> davidm wrote:
> | At the moment, there are two ways to control the unaligned message printing:
> | 
> |  - use the dmesg command to lower the printing threshold below KERN_WARNING
> |     ("dmesg -n4", IIRC)
> | 
> |  - use prctl --unalign=silent to turn off unaligned printing for a
> |    particular task and its children
> 
> Running prctl on relevant gettys at boot time would have the same effect.
> 
> grant


  parent reply	other threads:[~2003-10-08 22:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-08 14:42 user-space unaligned accesses Bjorn Helgaas
2003-10-08 21:46 ` Grant Grundler
2003-10-08 22:54 ` Bjorn Helgaas [this message]
2003-10-08 23:36 ` David Mosberger
2003-10-09 13:53 ` Bjorn Helgaas
2003-10-11 23:22 ` Micah Parrish
2003-10-13 23:56 ` David Mosberger
2003-10-13 23:59 ` Duraid Madina

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-106565367106363@msgid-missing \
    --to=bjorn.helgaas@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.