There's no such think as an Ideal cpu. It's like picking the right
religion :-) If you want a toy cpu, there are things like mmix.
In general true. But the real and toy CPUs are designed with the hardware
construction in mind, whereas the limitations deriving from HW (number of
registers, number of instructions, instruction complexity) may be less
relevant in the Qemu case. Also Qemu could benefit from getting information
analysed from the source code that no real HW needs. For example, perhaps
the TB state could be managed explicitly by the compiler.
Though I doubt the near native speed performance with kqemu can ever be
exceeded with a translator even with all compiler assistance tricks. For
other goals (like enhancing security), different methods could be tried, for
example it's hard for virus writers to target a dynamic or even encrypted
instruction set. Or make stack exploits difficult by giving the CPU separate
stack pointers for function arguments, return addresses and local variables.
_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.com/
_______________________________________________
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
