Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <tausq@debian.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: joel.soete@freebel.net, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] compiling kernels with gcc-3.1
Date: Mon, 15 Jul 2002 09:22:30 -0700	[thread overview]
Message-ID: <20020715162230.GJ8724@tausq.org> (raw)
In-Reply-To: <200207151524.g6FFOqqE023640@hiauly1.hia.nrc.ca>

> This is just a guess but I will wager that this problem is related
> to the problems with expect, the cc1plus crash and the mmap issues noted
> elsewhere with SMP kernels.  There seem to be circumstances where the
> kernel crashes when a user application traps unexpectedly.

in at least some of the cases, i've seen one CPU is processing an
unaligned trap for a kernel space insn. i don't see how the particular
pieces of code that's causing the trap are unaligned tho (eg.
search_exception_table).

One thing about the unaligned handler is that it wlil fail silently
while handling "non-trivial" load/store insns. For example, it doesn't
handle the ma/mb or m/sm completors for displacement/indexed
load/stores.

It is possible that we haven't needed these in the past for kernel-space
with gcc-3.0, but gcc-3.[12] have different optimizations that
generate these instructions which we do not handle properly in unaligned
cases. Although I think this may just be masking an underlying problem.

I'm working on a more complete unaligned handler to see if that makes a
difference. Unfortunately I've found that sometimes when the kernel code
is modified in trivial ways (adding printk's, etc) the behaviors become
quite different. This definitely suggests some kind of cache flushing
problem as Grant described elsewhere.

randolph

  parent reply	other threads:[~2002-07-15 16:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-12  7:36 [parisc-linux] compiling kernels with gcc-3.1 Randolph Chung
2002-07-12  9:49 ` joel.soete
2002-07-12 15:01   ` Randolph Chung
2002-07-12 16:23     ` joel.soete
2002-07-15  7:03       ` joel.soete
2002-07-15  7:24         ` joel.soete
2002-07-15 15:06           ` Randolph Chung
2002-07-15 15:56             ` joel.soete
2002-07-15 15:24         ` John David Anglin
2002-07-15 15:52           ` joel.soete
2002-07-15 16:22           ` Randolph Chung [this message]
2002-07-15 17:13             ` John David Anglin
2002-07-15 17:27               ` joel.soete
2002-07-13  5:20 ` [parisc-linux] compiling kernels with gcc-3.2 Randolph Chung
2002-07-13 10:24   ` Joel Soete
2002-07-13 18:54   ` Carlos O'Donell
2002-07-13 17:06 ` [parisc-linux] compiling kernels with gcc-3.1 Joel Soete
     [not found] <no.id>
2002-07-15 17:21 ` John David Anglin
2002-07-15 17:32   ` Randolph Chung
2002-07-15 17:43     ` Matthew Wilcox
2002-07-15 18:18       ` John David Anglin
2002-07-16  9:02   ` joel.soete

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=20020715162230.GJ8724@tausq.org \
    --to=tausq@debian.org \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=joel.soete@freebel.net \
    --cc=parisc-linux@parisc-linux.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