Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Randolph Chung <randolph@tausq.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] SMP kernel problems on a D350
Date: Sat, 21 Sep 2002 18:57:14 -0600	[thread overview]
Message-ID: <20020922005714.07CB24829@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Randolph Chung <randolph@tausq.org> of "Sat, 21 Sep 2002 16:20:18 PDT." <20020921232018.GA29388@tausq.org>

Randolph Chung wrote:
> legolas:/home/randolph# cat /proc/sys/kernel/unaligned 
> Unaligned trap handler is enabled
> legolas:/home/randolph# ./t; echo $?
> 0
> legolas:/home/randolph# echo 0 >> /proc/sys/kernel/unaligned 

Cool!
After reviewing the diff (on ftp.p-l.o/patches), only two nits
that have nothing to do with the code:

o cat output should relate to what I have to "echo" into the /proc file.
  ie only display '0' or '1' when catting.
  Or is "blah is enabled" by convention?

o SYSCTL_FILENAME should be "sys/kernel/unaligned_trap"
  and then I think 0 or 1 should be clear enough to anyone
  daring to mess with it.


> if someone can review this real quick before i commit it to cvs,

If you don't like my suggestions, I'm ok with committing
what you've already got.

> i'd
> appreciate it. in particular, the point where it decides that the
> unaligned trap is not enabled and forces the SIGBUS is not exactly at
> the beginning of the trap handler -- it still prints the unaligned
> message.... 

hmmm...if running under a debugger, one gets that info anyway.
But that's not always easy to do. I think it's ok since we don't
like to see unligned traps happen anyway.

Maybe a "unaligned_trap_msg" tunable?
/me runs...

thanks
grant

  reply	other threads:[~2002-09-22  0:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200209190805.KAA0000032531@simba.sch.bme.hu>
2002-09-19  9:17 ` [parisc-linux] SMP kernel problems on a D350 Istvan Gyenes
2002-09-19 12:21   ` J.Steindlberger
2002-09-19 12:29     ` Ryan Bradetich
2002-09-19 22:46   ` Grant Grundler
2002-09-20  8:28     ` Istvan Gyenes
2002-09-20 19:48       ` Carlos O'Donell
2002-09-20 20:02         ` Jeremy Drake
2002-09-20 20:37           ` Carlos O'Donell
2002-09-20 20:46             ` John David Anglin
2002-09-20 20:50               ` Randolph Chung
2002-09-20 20:55                 ` Carlos O'Donell
2002-09-21 23:20                   ` Randolph Chung
2002-09-22  0:57                     ` Grant Grundler [this message]
2002-09-20 20:55                 ` John David Anglin
2002-09-20 21:51                   ` Randolph Chung
2002-09-21  3:38             ` [parisc-linux] malloc limits John David Anglin
2002-09-21  4:14               ` Matthew Wilcox
2002-09-21  4:46                 ` Grant Grundler
2002-09-21  5:24                   ` John David Anglin
2002-09-21 22:33                     ` Grant Grundler
2002-09-22  5:43                       ` John David Anglin
2002-09-20 20:37           ` [parisc-linux] SMP kernel problems on a D350 Bdale Garbee
2002-09-20 20:52             ` Carlos O'Donell
2002-09-20 23:11             ` Jeremy Drake
2002-09-20 23:46               ` Jeremy Drake
2002-09-20 23:55               ` Robert Stanford
2002-09-21  4:31       ` Grant Grundler
     [not found] <20020921044102.3DD104829@dsl2.external.hp.com>
2002-09-23 17:23 ` Jeremy Drake
2002-09-19  7:38 Istvan Gyenes

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=20020922005714.07CB24829@dsl2.external.hp.com \
    --to=grundler@dsl2.external.hp.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=randolph@tausq.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