News for hackers. Stuff that matters.
Re:What have we lost? [video] by pjc50 on Wednesday April 07, 2021 @09:44AM (#26724805)
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)

Re:What have we lost? [video] by thequux on Wednesday April 07, 2021 @09:54AM (#26724966)
You'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.

Re:What have we lost? [video] by rjsw on Wednesday April 07, 2021 @12:22PM (#26727124)
The closest modern equivalent is probably a paravirtualized unikernel.
Re:What have we lost? [video] by hestefisk on Wednesday April 07, 2021 @10:56AM (#26725837)
It was intentionally designed as a single user mode-machine wasn’t it?
Re:What have we lost? [video] by db48x on Wednesday April 07, 2021 @11:47AM (#26726619)
Absolutely. There was no isolation between programs. In fact, you could write new programs by reusing parts of existing programs.
Re:What have we lost? [video] by rjsw on Wednesday April 07, 2021 @12:09PM (#26726952)
None 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.