From: David Huggins-Daines <dhd@eradicator.org>
To: rhirst@linuxcare.com
Cc: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] signal.c, etc
Date: 17 Dec 2000 14:41:39 -0500 [thread overview]
Message-ID: <87zohuhm30.fsf@cepstral.com> (raw)
Hi,
Just reading through the archives, I noticed you came upon my rather
hackish IAOQ manipulation in signal.c.
If you guys need any explanation about the intent of that code please
ask me. (I'm back on the parisc-linux list now, BTW)
I freely admit that it is bogus (in fact that's why the comment was
there), not because I didn't know which part of IAOQ was front and
which was back, but because:
(a) There are two different signal exit paths, one from interruptions,
one from system calls. This complicates things *tremendously*.
However, exiting from a signal handler always goes via system
calls, and in that case, the stored IAOQ values are meaningless.
I probably should have removed all the meaningless frobbings of
the stored IAOQ, but ... well ... time passes, you become occupied
elsewhere, etc.
(b) I don't understand what the processor actually does when you
restore IAOQ on exit from an interruption. The HP documentation
is not written in a particularly lucid manner.
(c) Setting iaoq_back to iaoq_front + 4 is *not* the right answer
because you may have taken an interruption in a branch, or an insn
may have been nullified, etc.
(d) I had about ten billion other things to do at the time and was
under lots of pressure to get "more important things" working...
--
David Huggins-Daines - dhd@eradicator.org
next reply other threads:[~2000-12-17 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-17 19:41 David Huggins-Daines [this message]
2000-12-20 9:14 ` [parisc-linux] signal.c, etc Richard Hirst
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=87zohuhm30.fsf@cepstral.com \
--to=dhd@eradicator.org \
--cc=parisc-linux@thepuffingroup.com \
--cc=rhirst@linuxcare.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.