All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: grundler@dsl2.external.hp.com (Grant Grundler)
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	Randolph Chung <randolph@tausq.org>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] 2.5 randomly kills applications with page faults
Date: Fri, 20 Dec 2002 19:46:57 -0600	[thread overview]
Message-ID: <200212210146.gBL1kvv11019@localhost.localdomain> (raw)
In-Reply-To: Message from grundler@dsl2.external.hp.com (Grant Grundler) of "Fri, 20 Dec 2002 18:38:24 MST." <20021221013824.GA18983@dsl2.external.hp.com>

grundler@dsl2.external.hp.com said:
> where STREGM/LDREGM are new macros that use st<X>,ma instructions.

Actually, I found STREG,ma and LDREG,mb worked for me.

grundler@dsl2.external.hp.com said:
> but, given the assertion we could take an interrupt between line 96 and
> 107, would an interrupt between 95/96 cause Bad Things (tm) to happen?

Not according to the parisc assembler manual.  As long as we can guarantee 
that the stack is incremented before the value is stored (which seems to be 
what STREG,ma seems to assure), we should be fine.

James

  reply	other threads:[~2002-12-21  1:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-18 16:37 [parisc-linux] 2.5 randomly kills applications with page faults James Bottomley
2002-12-18 17:02 ` Randolph Chung
2002-12-20 22:12   ` James Bottomley
2002-12-20 22:19     ` John David Anglin
2002-12-20 22:37     ` Grant Grundler
2002-12-22  7:11       ` Grant Grundler
2002-12-22 10:17         ` Helge Deller
2002-12-22 16:35         ` James Bottomley
2002-12-21  1:38     ` Grant Grundler
2002-12-21  1:46       ` James Bottomley [this message]
2002-12-21  4:34         ` Grant Grundler
2002-12-21  5:03           ` James Bottomley

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=200212210146.gBL1kvv11019@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=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 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.