Ich muss mir unbedingt merken, dass die langsame Reaktion auf IPIs, die in QEMU KVM nicht über Hypercalls ausgelöst werden, die Performance katastrophal beeinträchtigen kann, wenn ich das nächste Mal einen Kernel mit QEMU als Zielsystem schreibe. Mir graut es davor, herauszufinden, ob QEMU MTTCG ähnlich betroffen ist, da es im Mainline-QEMU keine solche Hypercalls gibt.

I need to make a mental note of the fact that slow responsiveness to IPIs not issued via hypercall in qemu KVM can pathologically degrade performance for the next time I'm writing a kernel using qemu as a target system. I'm terrified of finding out whether qemu MTTCG is similarly affected, because it has no such hypercalls in mainline qemu.

#Telix #QEMU #KVM #MTTCG #paravirtualisation #paravirtualization #hypercall #hypervisor #scheduling

The state of #insecurity of #proprietary #games is somewhat complicated to come-up with a good answer to.

Most engines used for games elide any notion of memory safety, so that's already a bad start.

Most OSes they run on provide far too much #AmbientAuthority as well.

Virtualization might be an idea but unfortunately #GPU #security with passthrough is problematic https://news.ycombinator.com/item?id=26380051 .

That leaves #paravirtualization, which is complex and so that's another problem.

Shit's fucked yo.