- 73comments
- 139comments
- 35comments
- 106comments
- —discuss
- 12comments
- 57comments
- 325comments
- —discuss
- —discuss
- 47comments
- 62comments
- 27comments
- 155comments
- 629comments
- 249comments
- 97comments
- 173comments
- 78comments
- 10comments
- 239comments
- 52comments
- 146comments
- 165comments
- —discuss
- 21comments
- 28comments
- 73comments
- 30comments
- 48comments
For some reason I thought the reason that this hadn't been implemented already was that Sony had patents on multithreaded binary translation. I guess those might have only applied to specific techniques for heterogeneous or ring-bus systems (i.e. Cell), though.
No, it's just that it's the kind of feature that's quite hard to retrofit to an existing design, since it breaks existing assumptions in a lot of places. And it's only relatively recently that the kind of embedded board that you usually want to emulate with QEMU has had a multi-core CPU.
This has recently landed in upstream qemu and will be available with the 2.9 release.
Some bugs are being found that affect single-vCPU emulation. There's still a possibility that it will be reverted before the release.
does this mean one could run (without hardware support, say in aws) smp virtualization? i.e. linux on linux or windows on linux (why not just spawn another machine? because you want to have more control than what aws provides)
This allows you to create one host thread per guest vcpu, so yes, you can run a smp guest on aws. But, it will be pretty slow compared to KVM, since the execution of the threads is limited by the host cpu resources and the fact that you are using translation and full system emulation.
so I guess that means QEMU always does full translation instead of just translating the privileged ops? (ala what vmware's innovation back in the day was)
It means that you can run SMP guest on SMP system and use more than one host core for that. You could run SMP guests before, but they were limited to only one host thread.
Here is a paper from last month's CGO2017 conference, explaining the techniques more in detail: http://www.cs.columbia.edu/~cota/pubs/cota_cgo17.pdf