4 ms·
How does that work when you drop to the debugger in the middle of an interrupt handler? A page fault? A task switch? How does the privilege separation work for
by pjc50 6y ago
How does that work when you drop to the debugger in the middle of an interrupt handler? A page fault? A task switch?
How does the privilege separation work for that environment?
(mostly rhetorical questions)
- thequux 6y agoYou'd think I was an expert, given that I gave that segment of the talk, but I haven't yet dived that deep into Genera's internals. As I understand it though, you don't have the concept of page faults at the image level; IIRC, Genera doesn't have any form of virtual memory, or if it does, it's all in microcode. Task switches are, iirc, handled in the image, but in the same way that it's done in Smalltalk: there's a function in the "kernel" to decide what task to switch to next, but the actual context switch is handled in microcode. Also, there's no such thing as privilege separation; everything's running in a single address space and namespacing is handled using Common Lisp's package system.
- hestefisk 6y agoIt was intentionally designed as a single user mode-machine wasn’t it?
- db48x 6y agoAbsolutely. There was no isolation between programs. In fact, you could write new programs by reusing parts of existing programs.
- rjsw 6y agoThe closest modern equivalent is probably a paravirtualized unikernel.
- rjsw 6y agoNone of those actions were visible to the virtual machine that contained the debugger. The CPU didn't even have the concept of an interrupt. The MIT Lisp Machine ran a simple kernel written in assembler that also included an interpreter for the user-visible instruction set, it would check periodically whether devices had raised an interrupt then return back into Lisp to handle the event.