4 ms·
A bit limited, as it's only for 32 bits x86, something the topic doesn't mention. There is no example of supported hardware, so at first glance It seems it wou
by buserror 11y ago
A bit limited, as it's only for 32 bits x86, something the topic doesn't mention.
There is no example of supported hardware, so at first glance It seems it would only be useful on old hardware, or Soekris-like boxes...
- calgoo 11y agoFrom his other project metioned by baruch: "Requiring each program to include drivers for every possible hardware device would be madness, and slow madness since device emulation is tricky and expensive. These programs are never going to be run on bare metal anyway, so I’m going to ignore all legacy PC devices and define the ‘fleet’ system interface a consisting solely of virtio devices. These devices all have a simple, standardized IO interface, so it should be no problem to build drivers for six or eight of them into my kernel-library. I’ll offer an efficient low-level I/O API for nonblocking DMA transfers. All the clunky, synchronous, blocking C APIs can be implemented on top of that."
- buserror 11y agoXvisor [ http://xhypervisor.org/ http://xhypervisor.org/ ] does that (plus many other things) -- I do like the virtio driver layer a lot; however in the case of Xvisor, you also get CPU virtualisation as well as IO drivers -- it's also portable across quite a few platforms.