From: Philipp Rumpf <prumpf@suse.de>
To: LaMont Jones <lamont@security.hp.com>
Cc: Grant Grundler <grundler@cup.hp.com>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] 715/100 data page fault and msg output
Date: Fri, 17 Sep 1999 03:52:57 +0200 [thread overview]
Message-ID: <19990917035257.K8112@suse.de> (raw)
In-Reply-To: <19990917013948.39E7E18711@security.hp.com>; from LaMont Jones on Thu, Sep 16, 1999 at 07:39:47PM -0600
> > we don't save them at all, but directly read them. Of course, printing them
> > doesn't make any sense (except for debugging the interruption code).
>
> Reading them when PSW.Q=1 is undefined, and it sounds like that's where the
> problem is coming from....
erm. yes, I know that. Yes, I said it doesn't make any sense.
> IIR should have had a load or store in it for Grant's problem...
Grant's problem is most likely solved. And no, there is no reason to save
IIR right now (there might be one when we have to find out whether a read or
write failed).
Philipp Rumpf
next prev parent reply other threads:[~1999-09-17 4:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-16 21:58 [parisc-linux] 715/100 data page fault and msg output Grant Grundler
1999-09-16 22:32 ` Philipp Rumpf
1999-09-16 23:22 ` Grant Grundler
1999-09-16 23:32 ` Philipp Rumpf
1999-09-17 1:05 ` Ryan Bradetich
1999-09-17 1:34 ` [parisc-linux] C200 support Grant Grundler
1999-09-17 3:02 ` Ryan Bradetich
1999-09-16 22:44 ` [parisc-linux] 715/100 data page fault and msg output LaMont Jones
1999-09-16 22:55 ` Philipp Rumpf
1999-09-17 1:39 ` LaMont Jones
1999-09-17 1:52 ` Philipp Rumpf [this message]
1999-09-17 21:48 ` Grant Grundler
1999-09-22 11:48 ` [parisc-linux] 715/80 problems Hannu Martikka
1999-09-22 13:35 ` Philipp Rumpf
1999-09-22 14:27 ` Hannu Martikka
1999-09-22 14:29 ` Philipp Rumpf
1999-09-22 14:31 ` Grant Grundler
1999-09-22 15:15 ` Hannu Martikka
1999-09-22 17:00 ` Alex deVries
1999-09-22 13:42 ` Grant Grundler
1999-09-22 15:18 ` Hannu Martikka
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=19990917035257.K8112@suse.de \
--to=prumpf@suse.de \
--cc=grundler@cup.hp.com \
--cc=lamont@security.hp.com \
--cc=parisc-linux@thepuffingroup.com \
/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.