From mboxrd@z Thu Jan 1 00:00:00 1970 From: peter@rulingia.com (Peter Jeremy) Date: Fri, 25 Mar 2016 09:50:49 +1100 Subject: [TUHS] Early non-Unix filesystems? In-Reply-To: <56F3BEAE.9060903@update.uu.se> References: <56F3BEAE.9060903@update.uu.se> Message-ID: <20160324225049.GA54792@server.rulingia.com> On 2016-Mar-24 11:17:18 +0100, Johnny Billquist wrote: >It is the normal behavior of any instruction that interrupts are not >recognized until the next instruction fetch. This is how the microcode >works, and it is also pretty much the same in any processor today. ... >individual instructions. You still get a fetch between each instruction, >at which point, interrupts will be recognized. Some instructions inhibit the "check for interrupts at the end of this instruction" check. I'm most familiar with the 8080 EI instruction, which enabled interrupts after the following instruction (so things like EI;HLT didn't have a window). It seems the PDP-11 SPL behaves the same. >memory access to get the actual content. The fun thing happens if you >set the indirect bit, and give your own address. This is then an >infinite memory reference. And the KA10 can not be broken out of that >lookup. The only solution is to pull the power plug. I can't think of any modern architectures that still support this sort of indefinite indirection but I know the ITT 3200 (custom CPU for controlling telephone exchanges) could do this. In it's case, a normal front-panel reset would recover. -- Peter Jeremy -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 949 bytes Desc: not available URL: