As mentioned above, no interruptions of tasks are possible. No MMU, every process and the kernel lives in the same - address space. Wasm is a more or less a strict Harward architecture, where code can be loaded but not modified at + address space. Wasm is a more or less a strict Harvard architecture, where code can be loaded but not modified at runtime. JIT compilation could in theory still work, you would just need to compile the code before launching it, but no runtime patching would be allowed (for example, the jump label kernel feature would not work well).
@@ -260,4 +260,4 @@ Examples: ls watch uptime head /proc/cpuinfo clone-based vforks, unlike in traditional vforks where the double-return on the same stack forbids this). -