[bflesch]

Sorry this might be an extremely stupid question, but can you please explain the benefits of this and what other (larger?) alternatives are?

I understand that this "exokernel" provides more performant hardware access for software and it seems to be written from scratch in assembler.

Does this mean that one should expect a lot of security and robustness issues, which means it should only be used for internal services and never be exposed to untrusted networks?

[awesomeMilou]

One thing that comes to mind is latency in a HPC context.

If you can fit your entire software stack into L3 cache, you never have to access memory and benefit from insanely good latency.

This was a thing in HFT like ~5-7 years ago, where you might have bought a 28 core Xeon, disable all but one or two cores and benefit from ~30mb L3 cache, which can fit an entire Linux Kernel, an SSH server and your trading software.

[heliumtera]

If one decides to boot an arbitrary system, pointing at whatever would be the latest version of exec.asm, it doesn't even matter what the project is today and whatever the setup script is doing. If one chooses to use this, one decides to handover the virtual machine ownership. Your system is whatever OP decides, now or in the future.

Edit: made a clear mistake here. One would clearly not be booting on lates version of exec.asm. It would be libBareMetal.asm instead.

Sorry for confusion guys, totally safe and effective

if [ -x "$(command -v curl)" ]; then curl -s -o libBareMetal.asm https://raw.githubusercontent.com/ReturnInfinity/BareMetal/m... else wget -q https://raw.githubusercontent.com/ReturnInfinity/BareMetal/m... fi