From: "Boyd Roberts" <boyd@fr.inter.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Nextstaion as plan9 terminal
Date: Mon, 24 Sep 2001 19:36:29 +0200 [thread overview]
Message-ID: <005801c1451f$7205a5c0$a2b9c6d4@SOMA> (raw)
In-Reply-To: <20010924172455.5597119A73@mail.cse.psu.edu>
> We also had continuing problems with backing out of interrupts:
> the processor didn't take interrupts between instructions. Instead
> you had to figure out the state of the machine and back it out by hand.
> We were pretty good at this but I remember there still being a lingering
> problem.
reminds me of the early 68020s. apart from the n too many interrupt
stacks frames there was a scary piece of assembler to mangle the
frame and then resume -- nasty.
next prev parent reply other threads:[~2001-09-24 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-24 17:24 presotto
2001-09-24 17:36 ` Boyd Roberts [this message]
2001-09-24 18:28 ` Jon Snader
-- strict thread matches above, loose matches on Subject: below --
2001-09-24 20:43 jmk
[not found] <matthias@mteege.de>
2001-09-24 14:19 ` Matthias Teege
2001-09-24 14:36 ` James A. Robinson
2001-09-24 16:58 ` Frank da Cruz
2001-09-24 17:00 ` Boyd Roberts
2001-09-24 17:16 ` William K. Josephson
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='005801c1451f$7205a5c0$a2b9c6d4@SOMA' \
--to=boyd@fr.inter.net \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).